Authorix API is a four-endpoint 📝REST interface for querying the 📝Authority Index, returning ranked human experts, full profiles, and peer networks as structured data.

The API is the programmatic face of 📝Authorix and the surface its consumer tools are built on. It is designed for grounding AI retrieval in identity-resolved expertise rather than web snippets: a query returns indexed entities with stable identifiers and rank positions, not generated prose. Typical uses are ranking crawled content by author authority, sourcing credible creators for outreach, feeding expert lists into research pipelines, and verifying that a handle belongs to someone the field actually recognizes. Billing is usage-based with no minimums and no seat licenses.

Prerequisites

• API key — Issued per organization from the Authorix dashboard; the same key authenticates the MCP server.
• Positive balance — Requests are rejected when the organization's balance runs out, independent of rate limits.
• Free credits — New accounts start with $5 in credits and no credit card required.
• SDU identifiers — The Authority Index's stable entity IDs, returned by search and required by the detail endpoint.

Interface

Base URL is https://api.authorix.com. Every request carries Authorization: Bearer <api_key>. Keys are scoped to an organization, and rate limits apply across all endpoints and all keys belonging to that organization.

GET /api/v1/index

Full-text search across the Authority Index. Returns ranked authorities for a topic, keyword, or niche.

Parameters:

• query (string, required) — the topic, keyword, or niche to search
• alpha2 (string, optional) — two-letter country code to constrain results; 23 countries are exposed in the playground
• limit (integer, optional, default 10) — number of results; see the note below on the effective ceiling

Response (200):

{
  "results": [
    {
      "sdu": 294152,          // stable authority identifier
      "name": "…",
      "rank": 1,              // position within the ranked result set
      "country_name": "…",
      "topic": "…"            // primary expertise area
    }
  ],
  "duration": 0.0,            // query processing time
  "request_id": "…"
}

GET /api/v1/detail

Retrieves full profiles for one or more authorities by identifier.

Parameters:

• sdus (string, required) — comma-separated SDU identifiers

Response (200):

{
  "sdu": 294152,
  "name": "…",
  "bio": "…",
  "country": "…",
  "topics": ["…"],
  "socials": { "platform": { "handle": "…", "followers": 0 } },
  "duration": 0.0
}

GET /api/v1/match

Verifies whether a social handle belongs to a ranked authority. The lookup behind the Verify product.

Parameters:

• handles (string, required) — the social handle to resolve

Response (200): the matched authority profile with name, rank, country, and core topic.

GET /api/v1/peers

Maps the influence circle around a handle, returning the ranked authorities connected to it.

Parameters:

• handles (string, required) — the social handle whose network to map

Response (200): a ranked list of connected authorities.

Code Examples

The simplest call — search the index for a topic and take the top ten:

curl -H "Authorization: Bearer $AUTHORIX_API_KEY" \
  "https://api.authorix.com/api/v1/index?query=mRNA%20therapeutics&limit=10"

Search, then hydrate the top result into a full profile:

import os, requests
H = {"Authorization": f"Bearer {os.environ['AUTHORIX_API_KEY']}"}
B = "https://api.authorix.com/api/v1"
hits = requests.get(f"{B}/index", headers=H,
                    params={"query": "climate finance", "alpha2": "NL", "limit": 5}).json()
sdus = ",".join(str(r["sdu"]) for r in hits["results"])
profiles = requests.get(f"{B}/detail", headers=H, params={"sdus": sdus}).json()
print(profiles)

Error Handling

• 403 Forbidden — insufficient balance — Returns "Your balance is too low. Please top up to continue using the service." Top up from the dashboard; this is separate from throttling.
• 403 Forbidden — invalid key — The key is rejected or its organization is not provisioned. Reissue from the dashboard rather than retrying.
• 429 Too Many Requests — Returns "Request was throttled." Limits are enforced per organization across all keys, so a second key does not raise your ceiling.
• Error messages are unstable — Authorix states the message text may change at any time and should not be relied on. Branch on status codes, never on strings.

Related

• 📝Model Context Protocol (MCP) — the protocol behind Authorix's MCP server, which wraps these same four endpoints.
• 📝Exa.ai — an adjacent retrieval API that returns web documents where this one returns ranked people.

Contexts

• 🏷️#authorix
• 🏷️#feature-of-authorix