Manifest Schema

Developer Manifest Schema

The Developer Manifest is submitted in Step 1 of registration (POST /v1/auth/verify-phone).

All fields are required.

Field	Type	Validation	Description
mobile_phone	string	E.164 format	Phone for OTP delivery. Not stored in public profile.
trust_tier	enum	`community` or `enterprise`	Agent trust tier
agent_name	string	Non-empty	Human-readable agent name
agent_version	string	Non-empty	Semantic version (e.g. `1.0.0`)
developer_name	string	Non-empty	Developer or organisation name
contact_email	string	Valid email	Contact email for badge correspondence
primary_goal	string	Non-empty	One-sentence description of the agent's purpose
tools	string[]	Array of strings	Tools / capabilities the agent uses
compliance_attestation	boolean	Must be `true`	Attestation of compliance with applicable regulations
data_residency	string	Non-empty	AWS region or datacenter (e.g. `us-east-1`)

Example Manifest

{
  "mobile_phone": "+15005550006",
  "trust_tier": "community",
  "agent_name": "Support Bot v2",
  "agent_version": "2.1.0",
  "developer_name": "Acme Corp",
  "contact_email": "agents@acme.com",
  "primary_goal": "Automated tier-1 customer support",
  "tools": ["web-search", "ticket-creation", "email"],
  "compliance_attestation": true,
  "data_residency": "us-east-1"
}

Public Profile

Step 1 returns a public_profile — the manifest minus mobile_phone and compliance_attestation. This is what gets embedded in the Agent Badge JWT and returned by GET /v1/manifest/{did}.