TETA+PI

TETA+PI is trust infrastructure for digital entities — verified people,
companies, APIs, AI models, MCP servers and agents, discoverable by AI agents.

This plugin lets a site owner:

• Connect the site to their TETA+PI entity with a personal API key.
• Prove domain ownership (DNS TXT record or a well-known file, whichever is
  easier) directly from the WordPress admin.
• Display a verified-entity badge anywhere via the [tetapi_badge] shortcode
  or the “TETA+PI Badge” widget.
• Make the site agent-readable: once connected, the plugin adds a
  machine-readable JSON-LD block to every page’s <head>, and serves
  /.well-known/agent.json, /.well-known/agent-card.json and /llms.txt
  from your own domain — so AI agents and crawlers (including ones that
  don’t execute JavaScript) can read your verified-entity data directly,
  not just see a visual badge.

Makes your site discoverable and verifiable by AI agents, LLMs and answer
engines (AEO/GEO) — not just search engines.

This release is 100% free — every feature above is fully functional with no
payment required. Two premium modules are planned for later: Module #1
($25) — additional badge styles, automatic placement, multi-entity support,
WooCommerce integration — and Module #2 ($52), a further tier coming
after that. Neither is for sale yet; the settings page shows what’s planned
and has a field to redeem a free code if TetaPi gives you one (e.g. as a
thank-you for a social-media shoutout).

Learn more at tetapi.dev.

External services

This plugin connects to api.tetapi.dev, the TETA+PI API. It is operated by
TetaPi GmbH, the same company that develops this plugin, and is required for
the plugin’s core functionality: connecting your site to your TETA+PI
entity, proving domain ownership, and displaying your trust badge.

What is sent, and when:

• When you save your Personal API Key under Settings > TETA+PI, that key is
  sent to GET /businesses to list the entities it can access. The key is
  stored encrypted at rest (using your site’s own WordPress salts), not in
  plain text.
• When you click “Start verification” or “Check now”, your site’s domain
  (auto-detected from your site URL) and your chosen entity ID are sent to
  POST /businesses/{id}/verify/domain/start and
  POST /businesses/{id}/verify/domain/check respectively, to prove you
  control the domain.
• Whenever the [tetapi_badge] shortcode or the “TETA+PI Badge” widget is
  displayed on any page, your connected entity’s slug is sent to the public,
  unauthenticated GET /businesses/by-slug/{slug}/public endpoint to fetch
  your badge data. This response is cached for 15 minutes (WordPress
  transient) to limit requests. No visitor-identifying data is sent — every
  visitor triggers the same request for the same public entity data.
• On every page load (for the JSON-LD block) and whenever
  /.well-known/agent.json, /.well-known/agent-card.json or /llms.txt
  is requested on your site, your connected entity’s ID is sent to the
  public, unauthenticated GET /wk/{entity_id}/* endpoints to fetch
  agent-readable data about your entity. Also cached for 15 minutes. No
  visitor-identifying data is sent.

No data is sent to any other third party.

Terms of Service: https://tetapi.dev/terms
Privacy Policy: https://tetapi.dev/privacy