Connect once.
Verify anything.
TETA+PI exposes verified entities via MCP (Model Context Protocol) and REST API. Your AI agent can verify businesses, journalists, and artists in one tool call.
For Claude, GPT, custom agents. Plug-and-play via SSE or stdio.
Standard JSON/HTTPS endpoints. Bearer token auth.
No CMS? One script tag makes any static site agent-readable.
Open-source library · MIT license · protocol spec
For AI agents — one config line.
Any MCP-compatible agent (Claude, GPT, custom) connects via SSE or stdio. Authenticated with Bearer token from your TETA+PI account.
"mcpServers": { "teta-pi": { "url": "https://mcp.tetapi.dev/sse", "apiKey": "YOUR_API_KEY" } }
mcp_servers: - name: teta-pi url: https://mcp.tetapi.dev/sse auth: Bearer $TETA_API_KEY
Direct HTTP endpoints.
Base URL: https://api.tetapi.dev/api/v1 — Bearer token from your account settings. Full schema at api.tetapi.dev/docs.
# Search for a verified entity curl https://api.tetapi.dev/api/v1/search \ -H "Authorization: Bearer $TETA_API_KEY" \ -G --data-urlencode "q=organic bakery Berlin" \ --data-urlencode "level=any" # Response [{ "id": "a7f3b9c2-...-...-...-............", "name": "GreenFarm GmbH", "slug": "greenfarm-gmbh", "entity_type": "business", "verification_level": "registry", "country": "DE", "block_count": 4, "agent_endpoint": "https://agents.greenfarm.de" }] # Fetch its cryptographic proof curl https://api.tetapi.dev/api/v1/businesses/a7f3b9c2-.../proof \ -H "Authorization: Bearer $TETA_API_KEY"
Build on the protocol.
The verification library, protocol spec, and MCP server reference implementation are MIT-licensed. Fork it, embed it, build on it.
Questions? Write to [email protected] — or open an issue on GitHub.