Skip to content
This repository was archived by the owner on Jul 14, 2026. It is now read-only.

teta-pi/protocol

Folders and files

NameName
Last commit message
Last commit date

Latest commit

Β 

History

3 Commits
Β 
Β 
Β 
Β 
Β 
Β 

Repository files navigation

πŸ—„ Archived 2026-07-14. This repo pre-dated the real implementation β€” README/LICENSE only, no code. Canonical docs (architecture, verification levels, MCP tools) now live in teta-pi/infra; the live implementation is teta-pi/api, teta-pi/mcp, and teta-pi/web. The connect URL below is also stale β€” the real one is https://mcp.tetapi.dev/sse.

TETA+PI Protocol (Θ+Ο€)

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.

The Problem

Agent protocols (MCP, A2A) handle connectivity. None handle identity, verification, or provenance.

The Solution

A central trust registry where entities establish cryptographically verified identities. AI agents query it via MCP before interacting with any entity.

Verification Levels

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 Integration

mcp_servers:
  - name: teta-pi
    url: https://tetapi.dev/mcp
    auth: Bearer

MCP Tools

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

Architecture

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

Trust Architecture

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.

License

MIT License Β© 2026 TETA+PI Β· tetapi.dev

Verification = Visibility. Without verification, an entity does not exist in Agent Internet for agents.

About

πŸ—„ Archived 2026-07-14 β€” superseded by teta-pi/infra (canonical docs) and the live teta-pi/{api,web,mcp} implementation

Topics

Resources

License

Stars

1 star

Watchers

0 watching

Forks

Releases

No releases published

Packages

 
 
 

Contributors