ANHA Registry API

ANHA Registry API as documented publicly: 11 operations. Contract generated from the documentation by API Evangelist (2026-11-01); not the provider's own document.

Operations 11

POST /anha POST /anha #
GET /v1/authenticity/{handle} Get authenticity for a handle #
GET /v1/brand/{handle} Get brand pack for a handle #
GET /v1/federation/record/@myagent.ai GET /v1/federation/record/@myagent.ai #
GET /v1/industries List ANHA industries #
POST /v1/invoke Invoke a capability on a handle #
GET /v1/invoke/{requestId} Poll an invocation request #
GET /v1/reputation/{handle} Get reputation for a handle #
GET /v1/resolve Resolve a handle #
GET /v1/resolve/@nike.ai GET /v1/resolve/@nike.ai #

Work with this as data

Every API here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for apis

7 MCP tools reach this
  • find_apisBrowse and filter every API in the catalog.
  • get_api_artifactsOne API's artifacts, grouped by type.
  • get_openapiThe primary OpenAPI for this API.
  • find_similar_apisAPIs that look like this one.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This API
curl "https://apis.io/api/v1/apis/anha-ai:anha-ai-api"
All apis
curl "https://apis.io/api/v1/apis?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

A second provider on the same verified email joins the account you already have.

OpenAPI Specification

anha-ai-openapi-generated.yml Raw ↑
openapi: 3.1.0
info:
  title: ANHA Registry API
  version: '2026-11-01'
  description: 'GENERATED FROM DOCUMENTATION by API Evangelist on 2026-11-01: 11 operation(s) read from 6 public documentation page(s) (each operation
    names its page in x-source). This is not the provider''s published contract; ANHA Registry has published no machine-readable contract that
    the pipeline could find. Engine: oss.'
  x-evidence-tiers:
    code-example: 3
    documentation: 8
    pages-with-code: 5
    pages-read: 6
  x-generated-from: documentation
  x-provenance: generated
  x-authored-by: API Evangelist
  x-generated: '2026-11-01'
  x-generator: generate-contract-from-docs.py
  x-engine: oss
  x-sources:
  - https://anha.ai/tutorial
  - https://anha.ai/tutorial/grok
  - https://anha.ai/tutorial/claude
  - https://anha.ai/tutorial/gemini
  - https://anha.ai/tutorial/own-agent
  - https://anha.ai/tutorial/serve-agent
servers:
- url: https://resolver.anha.ai
paths:
  /anha:
    post:
      operationId: post_anha
      tags:
      - Anha
      summary: POST /anha
      x-source: https://anha.ai/tutorial/serve-agent
      responses:
        '201':
          description: Success (status as documented)
      x-evidence:
        kind: code-example
        language: curl
        snippet: curl.exe instead of curl. Terminal Copy curl -s -X POST https://agent.example.com/anha -w " %{http_code}"
  /v1/authenticity/{handle}:
    get:
      operationId: get_v1_authenticity_handle
      tags:
      - Authenticity
      summary: Get authenticity for a handle
      x-source: https://anha.ai/tutorial
      parameters:
      - name: handle
        in: path
        required: true
        schema:
          type: string
      responses:
        '200':
          description: Success (status as documented)
      x-evidence:
        kind: documentation
  /v1/brand/{handle}:
    get:
      operationId: get_v1_brand_handle
      tags:
      - Brand
      summary: Get brand pack for a handle
      x-source: https://anha.ai/tutorial
      parameters:
      - name: handle
        in: path
        required: true
        schema:
          type: string
      responses:
        '200':
          description: Success (status as documented)
      x-evidence:
        kind: documentation
  /v1/federation/record/@myagent.ai:
    get:
      operationId: get_v1_federation_record_myagent_ai
      tags:
      - Federation
      summary: GET /v1/federation/record/@myagent.ai
      x-source: https://anha.ai/tutorial/serve-agent
      responses:
        '200':
          description: Success (status as documented)
      x-evidence:
        kind: code-example
        language: curl
        snippet: 'curl https://resolver.anha.ai/v1/federation/record/@myagent.ai You should see {"error":"missing_header","error_description":"missing
          x-anha-timestamp"} 401

          {"version":3,"handle":{…},"public_key":"…","kem_public_key":"…","addresses":["https://agent.example.com/anha"],…} Then run a full round
          trip on your machine This builds the same encrypted call ANHA sends, runs it through your handler and decryp'
  /v1/industries:
    get:
      operationId: get_v1_industries
      tags:
      - Industries
      summary: List ANHA industries
      x-source: https://anha.ai/tutorial
      responses:
        '200':
          description: Success (status as documented)
      x-evidence:
        kind: documentation
  /v1/invoke:
    post:
      operationId: post_v1_invoke
      tags:
      - Invoke
      summary: Invoke a capability on a handle
      x-source: https://anha.ai/tutorial
      requestBody:
        required: true
        content:
          application/json:
            schema:
              $ref: '#/components/schemas/PostV1InvokeRequest'
      responses:
        '200':
          description: Success (status as documented)
      x-evidence:
        kind: documentation
  /v1/invoke/{requestId}:
    get:
      operationId: get_v1_invoke_requestId
      tags:
      - Invoke
      summary: Poll an invocation request
      x-source: https://anha.ai/tutorial
      parameters:
      - name: requestId
        in: path
        required: true
        schema:
          type: string
      responses:
        '200':
          description: Success (status as documented)
      x-evidence:
        kind: documentation
  /v1/reputation/{handle}:
    get:
      operationId: get_v1_reputation_handle
      tags:
      - Reputation
      summary: Get reputation for a handle
      x-source: https://anha.ai/tutorial
      parameters:
      - name: handle
        in: path
        required: true
        schema:
          type: string
      responses:
        '200':
          description: Success (status as documented)
      x-evidence:
        kind: documentation
  /v1/resolve:
    get:
      operationId: get_v1_resolve
      tags:
      - Resolve
      summary: Resolve a handle
      x-source: https://anha.ai/tutorial
      parameters:
      - name: id
        in: query
        required: true
        schema:
          type: string
        description: Handle identifier
      responses:
        '200':
          description: Success (status as documented)
      x-evidence:
        kind: documentation
  /v1/resolve/@nike.ai:
    get:
      operationId: get_v1_resolve_nike_ai
      tags:
      - Resolve
      summary: GET /v1/resolve/@nike.ai
      x-source: https://anha.ai/tutorial/grok
      responses:
        '200':
          description: Success (status as documented)
      x-evidence:
        kind: code-example
        language: curl
        snippet: curl https://resolver.anha.ai/v1/resolve/@nike.ai — a JSON record means the network is fine and the problem is in the client
          config. No response means ask for https://resolver.anha.ai/mcp to be allowed. An order or payment just hangs Cause — This is not a fault.
          The merchant requires phone approval, so the call returns a pending status with a request id. Fix — Approve it on your phone. A human
          dec
  /v1/search:
    get:
      operationId: get_v1_search
      tags:
      - Search
      summary: Search ANHA agents
      x-source: https://anha.ai/tutorial
      parameters:
      - name: capability
        in: query
        required: false
        schema:
          type: string
      - name: industry
        in: query
        required: false
        schema:
          type: string
      - name: limit
        in: query
        required: false
        schema:
          type: integer
      responses:
        '200':
          description: Success (status as documented)
      x-evidence:
        kind: documentation
components:
  schemas:
    PostV1InvokeRequest:
      type: object
      properties:
        handle:
          type: string
          description: Target handle
        capability:
          type: string
          description: Capability to invoke
        args:
          type: object
          description: Arguments for the capability
      required:
      - handle
      - capability
tags:
- name: Anha
- name: Authenticity
- name: Brand
- name: Federation
- name: Industries
- name: Invoke
- name: Reputation
- name: Resolve
- name: Search