Agxntsix Developers

The Agxntsix Content API is a public, read-only REST API over the articles, guides, glossary entries, reports, and comparisons published on agxntsix.ai. Use it to search our content from an agent, a script, or your own app.

Quickstart

No sign-up and no API key: the API is unauthenticated and read-only. Send a request to the base URL https://agxntsix.ai/api/v1.

curl "https://agxntsix.ai/api/v1/content?limit=3"

The full machine-readable description is the OpenAPI 3.1 spec at /openapi.json. Every operation has a unique operationId, so it can be loaded directly as LLM function-calling tools. There is no sandbox because the API has no writes; production is safe to explore.

Endpoints

GET /health

getHealth: Connectivity check. Returns {"status":"ok","version":"1"}.

curl https://agxntsix.ai/api/v1/health

GET /content

listContent: Published content summaries, newest first. Query: kind (blog, comparison, glossary, guide, report), limit (1-50, default 20), offset.

curl "https://agxntsix.ai/api/v1/content?kind=guide&limit=5"

GET /content/{kind}/{slug}

getContent: One published item with its full Markdown body, keywords, and citations.

curl https://agxntsix.ai/api/v1/content/glossary/voice-ai

Rate limits

Each client IP gets 60 requests per 60 seconds, counted per server instance. Every response reports the quota in the IETF RateLimit-Policy and RateLimit headers, plus X-RateLimit-Limit, X-RateLimit-Remaining, and X-RateLimit-Reset (seconds). Over the limit you get HTTP 429 with Retry-After.

RateLimit-Policy: "default";q=60;w=60
RateLimit: "default";r=59;t=42

Errors

Every 4xx and 5xx response is an RFC 9457 application/problem+json object with a stable, machine-readable code:

  • invalid_request
  • not_found
  • rate_limited
  • internal_error
HTTP/1.1 404 Not Found
Content-Type: application/problem+json

{
  "type": "https://agxntsix.ai/developers#error-not_found",
  "title": "Not found",
  "status": 404,
  "code": "not_found",
  "detail": "No published glossary with slug \"nope\".",
  "instance": "/api/v1/content/glossary/nope"
}

Versioning and deprecation

The major version is in the path (/api/v1) and echoed in the API-Version response header. New fields, endpoints, and enum values are added within v1, so ignore fields you do not recognize. Breaking changes ship as /api/v2. v1 then returns Deprecation (RFC 9745) and Sunset (RFC 8594) headers for at least 180 days before removal.

More machine-readable resources