Read-only by default
Anyone can use the public endpoint for profile search, reads, compare, trust explanation, site check, package manifest reads and checkout instructions.
No key required
Partner access
Public first. Partner access second.
AgntBase keeps the public A2A layer small and safe. Partners can later use an API key tier for higher read limits and access to the extended Agent Card, while action methods remain deferred behind auth and human confirmation.
Tiers
Two access layers
The split is deliberate: public discovery stays simple, while partner access can expose richer metadata without turning the public endpoint into a risky action surface.
Higher read limits + extended card
Partner access uses x-api-key. The first use case is not “more power”, but cleaner controlled reads and access to the extended Agent Card.
API key required
What changes
Partner layer in practice
The partner tier does not change the trust model. It only opens richer metadata and safer scaling for integrations that already have a real relationship with us.
| Header | x-api-key | Used to identify the partner tier. |
|---|---|---|
| Public endpoint | /a2a/jsonrpc | Same endpoint, different read limit behavior. |
| Extended card | /a2a/agent-card/extended | Returns partner-only metadata when a valid key is present. |
| Current benefit | Higher read limits | Useful for integrations, testing and catalog-style reads. |
| Future benefit | Richer metadata | Extended docs, tiered capabilities, partner signals and integration notes. |
Hard rule
What partner access still does not unlock
This is where we stay disciplined. Even a partner key should not silently turn a read layer into an autonomous action layer.
No automatic payments
Checkout instructions can be returned, but public or partner access does not charge, capture payment or place orders.
No outreach sending
Partner access is not a backdoor into messaging, mailouts or lead actions on behalf of businesses.
No write methods without confirmation
Future write-capabilities require auth, scope, logs and human confirmation. That rule stays in place.