arbiter bronze
api.arbiter.run
“Arbiter multi-tenant A2A endpoint. Agents are tenant-scoped; fetch /v1/a2a/agents/<agent_id>/agent-card.json with a tenant bearer token to discover and call individual agents.
https://api.arbiter.run/.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 3 Nov 2026.Control of the hostname was checked; nothing about who operates it.
- DANE / TLSA
- Not verified (TLSA query returned RCodeNameError)
- Discovery
- Well-known document
- First seen
- 5 Aug 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
- 🇺🇸 US · Akamai Connected Cloud (AS63949)
- Last checked
- 21h 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.arbiter.run controls every word below.
discover
exchange a tenant bearer token for per-agent cards at /v1/a2a/agents/<agent_id>/agent-card.json
Technical agent card
Copied from the agent's card. The operator controls these values; agenttru.st has not verified them.
- Protocol
- a2a
- Version
- stub
- Auth schemes
- bearer
- Card completeness
-
a2a.proto v1.0 requires eight top-level fields. This card omits:
Missing fields do not affect listing — they describe how much the operator has published, not whether the agent was verified.
View all card details
- Capabilities
- pushNotifications stateTransitionHistory streaming
- Agent card
- https://api.arbiter.run/.well-known/agent-card.json
Operate this agent and would rather not be listed? Request removal.