Make one live agent discoverable without overstating what it can do.

A focused identity and discovery workstream for a real deployed agent. We bind its public name to the organization, controller, domain, environment, capabilities, and incident path, then test every published claim against the live surface.

Apply for the sprint View the full Identity Pack

Price hypothesis: starting at $399 · Fixed scope before work begins

What is included

One agent, one truthful public surface

Organization, accountable controller, and agent identity map
Canonical domain and environment record
Capability, endpoint, authentication, and protocol inventory
Agent Card, OpenAPI, MCP, A2A, or registry metadata review where applicable
Cloudflare Web Bot Auth and public JWKS directory readiness when the live stack supports them
BotBase and MCP Registry submission preparation when current entry requirements are met
Live endpoint and advertised-capability checks
Public-safe discovery files and launch checklist
Incident, replacement, and revocation procedure

Entry conditions

The agent must already be real

A named organization and accountable natural-person controller
A deployed service, agent, or endpoint we can test
Customer control of the canonical domain and deployment
A clear list of intended capabilities and audiences
No request for private-key, seed-phrase, or reusable credential custody

If the service is not live yet, start with the readiness scan or the broader Identity and Discovery Pack.

Five-day working sequence

Day 1

Bind

Confirm organization, controller, agent, domain, and environment.

Day 2

Inventory

Map capabilities, endpoints, authentication, protocols, and claims.

Day 3

Test

Exercise the live surface and record scoped results.

Day 4

Publish

Prepare the smallest accurate set of discovery metadata.

Day 5

Operate

Prove incident, replacement, monitoring, and revocation paths.

What signed means here

Attributed records, customer-controlled keys

The sprint creates an attributed operating record and a signing plan for customer-controlled keys where signatures are useful. EIN.LLC does not become the agent operator, credential issuer, protocol authority, or private-key custodian.

“Designed for” a protocol or provider does not imply endorsement or partnership. A conformance statement names the exact surface, version, method, result, and date tested. No capability is published merely because a draft specification supports it.

Future beta · Applications open

Bring one agent and one live outcome

Joining the application list does not start paid work. We will confirm availability, the fixed scope, evidence, exclusions, schedule, and fee before a sprint begins.

Apply for the sprint