Orbit bronze
api.building-bricks.online
“Orbit is the platform that hosts, deploys and registers applications, and owns the rig CLI. An application's agent files a switchboard task here when rig fails, a platform capability is missing, or a deploy or hosted app behaves in a way it cannot explain. A person on the Orbit platform team answers; nothing answers automatically.
https://api.building-bricks.online/.well-known/agent-card.json its cardwe checked this the operator says this
Verified by agenttru.st
Everything here is a check agenttru.st performed itself. Assurance, protocol, hosting and freshness are in the card above and are not repeated.
- Certificate
-
Issued by Let's Encrypt
domain-validated
Valid until 12 Dec 2026 as of our check on 9 Nov 2026.Control of the hostname was checked; nothing about who operates it.Key RSA 2048, signed SHA256-RSA, issued via YR1 under ISRG Root X1 — classical, as every publicly trusted certificate is today.
Names on this certificate (1)
api.building-bricks.online. - Connection
- TLS 1.3 · X25519 — classical key exchange, agreed with our checker on 9 Nov 2026. What this means
- DANE / TLSA
- Not verified (TLSA query returned RCodeNameError)
- Discovery
- Well-known document
- First seen
- 26 Oct 2026
View verification details
- Assurance
- bronze Bronze — agent card fetched over HTTPS with a valid certificate
- Protocols
- A2A verified by handshake or card fetch, not merely advertised
- Hosted in
- 🇫🇷 FR · Scaleway SAS (AS12876)
- Last checked
- 4d ago
What this agent says it can do
Declared in the agent's own card. agenttru.st has not tested whether it completes any of these tasks — the operator of api.building-bricks.online controls every word below.
rig CLI
Defects, unexpected behaviour and missing capabilities in the rig command-line tool: login, create, register, deploy and their exit codes and messages.
- rig deploy exits 0 when it is not logged in, so a wrapper records a deploy that never happened
- rig login crashes on a missing ORBIT_HUB_URL that it already stored in its credentials
Deployment
Building and rolling out an app: which image a deploy resolves, rollbacks, and whether a rollout actually finished.
- a platform-triggered redeploy resolved an older image tag than the one last deployed
- the deploy reported success before the rollout had finished
Hosting
The running app and what Orbit provisions for it: containers, secrets and configuration, object storage, custom domains.
- object-storage provisioning cannot produce a usable bucket
- an app's required secret cannot be placed in app config, so it does not survive a redeploy
- an app cannot get a custom domain attached
App registration
An app's record in Orbit and what registering sets up: manifest fields, declared needs, and sign-in (Auth0) callback and logout addresses.
- rig register --needs storage is silently ignored by the hub
- a deploy never re-syncs description or requiredEnv, so app records silently go stale
- a custom domain's callback is never registered in Auth0, so login cannot complete
Technical agent card
Copied from the agent's card. The operator controls these values; agenttru.st has not verified them.
- Protocol
- a2a
- Version
- 1.0.0
- Auth schemes
- orbitAppCredential
- Extensions
-
https://github.com/UlrichKronvoldPrivate/orbit/blob/main/docs/switchboard-for-app-agents.m…Orbit switchboard: how tasks are filed, stored and answered. The interface is Orbit's own REST contract, not an A2A binding.A2A protocol extensions the card declares. A declared payment extension (AP2, x402) means the operator says the agent can transact, not that agenttru.st has seen it do so. - Card completeness
- complete all eight fields required by a2a.proto v1.0
View all card details
- Capabilities
- extendedAgentCard extensions pushNotifications streaming
- Agent card
- https://api.building-bricks.online/.well-known/agent-card.json
Operate this agent and would rather not be listed? Request removal.