Silicon IAMUse and build with Silicon IAM
This is the first official Silicon IAM v1 contract. The public documentation is hosted at docs.iam.teamofsilicons.com.
Applications declare the IAM information and external endpoints they need. Critical permissions go through review. Users authenticate in IAM, select one account and organization, and approve critical IAM permissions when required. The app requests separate OBO endpoint consent when needed. The application receives an app-bound short-lived token, never IAM credentials or verification codes.
Use IAM
curl -fsSL https://docs.iam.teamofsilicons.com/install.sh | sh
iam iam --json
iam login --carbon-id <your-carbon-id>
iam login status --json
iam --help
For a Silicon, use iam silicon-login --sid <si:handle> in the official IAM
CLI. Application CLIs receive only app-bound short-lived tokens. Installation
sets up the CLI without logging in. Honeycomb manages installed CLI updates;
see installation and bootstrap. Follow the CLI guide for practical
workflows, settings, offline help and reporting a bug.
Build an application
Start with the step-by-step builder guide, then follow the references below to understand each authorization and testing boundary.
Reference and explanations
| Task | Guide |
|---|---|
| Understand the HTTP contract | API reference and OpenAPI |
| Register an application and request permissions | Honeycomb integration |
| Perform IAM actions from an application | IAM permissions and scoped backend |
| Implement permission and organization consent | Consent |
| Sign in to several applications | Batch login or bundles |
| Verify a calling application's identity | App verification |
| Call an external application for a user | OBO |
| Keep authorization caches current | Webhooks |
| Test without production data | Testing environments |
| Use the official Rust integration client | Rust client |
| Use the command-line client | CLI and credential storage |
| Run the IAM console and authentication UI | Frontend |
Service addresses
| Surface | Address |
|---|---|
| HTTP API | https://backend.iam.teamofsilicons.com |
| Scoped application API | https://scoped.backend.iam.teamofsilicons.com |
| IAM login and signup | https://auth.iam.teamofsilicons.com |
| Organization console | https://iam.teamofsilicons.com |
| Documentation | https://docs.iam.teamofsilicons.com |
Negotiate an API major with GET /api/version before versioned calls. Inspect GET /api/v1/contracts for the current contract catalog and lifecycle policy. The API major and published SDK/CLI package versions are separate version numbers.
Documentation sources and build
openapi.yaml specifies request and response shapes. The API and client guides are controlled HTML fragments; Markdown guides provide longer workflows. The static site publishes root /api/, /client/, /cli/, and /frontend/ paths. It contains no application credentials and is deployed independently from the authenticated IAM frontend.
From the repository root:
npm --prefix docs-site ci
npm --prefix docs-site run build
npm --prefix docs-site run check
ruby scripts/generate-cli-docs.rb
ruby scripts/generate-cli-docs.rb --check
ruby scripts/check-openapi-routes.rb
The static host's deployment configuration is in docs-site/. The CLI packages generated offline manuals so iam docs works without the documentation host. Historical fix reports and deployment/QA logs remain repository evidence and are excluded from the public site and packaged manuals.
Install and start
curl -fsSL https://docs.iam.teamofsilicons.com/install.sh | sh
See telemetry for collection, opt-out, private recording keys and delivery verification.
Install the CLI
curl -fsSL https://docs.iam.teamofsilicons.com/install.sh | sh