The central trust registry for Agent Internet. As ICANN is for domains. As CA/Browser Forum is for SSL.
TETA+PI verifies any entity — business, journalist, creator, or organization — so AI agents can trust who they're talking to.
Agent protocols (MCP, A2A) handle connectivity. None handle identity, verification, or provenance.
A central trust registry where entities establish cryptographically verified identities. AI agents query it via MCP before interacting with any entity.
| Level | Name | Method |
|---|---|---|
| ●○○ L1 | Registry Attested | Cross-referenced with 21+ official registries |
| ●●○ L2 | Fully Verified | C2PA signed blocks + Bitcoin OpenTimestamps |
| ●●◌ L3 | Live Verified | Active PI Camera stream · real-time verification |
mcp_servers:
- name: teta-pi
url: https://tetapi.dev/mcp
auth: Bearer| Tool | Description |
|---|---|
search_entities |
Query verified entities by intent and jurisdiction |
get_entity_profile |
Resolve full verified profile with blocks and provenance |
verify_endpoint |
Verify an agent endpoint belongs to a declared entity |
get_verification_proof |
Return C2PA + Bitcoin timestamp proof chain |
resolve_intent |
Route a user intent to the right verified entity |
Entity Layer → Profile · Blocks · Privacy Toggle · EntityType
Verification Layer → C2PA · Bitcoin OpenTimestamps · Endpoint Verification
Protocol Layer → MCP Server · Intent Graph · /.well-known/agent.json · Root CA
TETA+PI operates as Root CA. Enterprise customers receive a delegated CA. Forks are welcome under MIT — but without the Root CA, third-party trust cannot be guaranteed.
This is the same model as the CA/Browser Forum: open standards, centralized trust anchor.
MIT License © 2026 TETA+PI · tetapi.dev
Verification = Visibility. Without verification, an entity does not exist in Agent Internet for agents.