Data & agents

AVGC-XR is built to be read by machines as well as people. The policy tracker and entity records are structured data with per-fact provenance, and they are available as JSON, as markdown, and through an MCP server that AI agents can call directly. AI crawlers are welcomed deliberately, not tolerated — see /llms.txt.

What’s available

Policy tracker
5 Indian state AVGC-XR policies with structured incentive terms — actual caps, eligibility and durations — each carrying its primary government source, an archived copy of that document, status and version. Nothing equivalent exists elsewhere.
Entity records
44 studios, institutes and events tracked on the wire. Curated facts (HQ, India locations, segments, parent organisation, official site) each carry their own source URL and verification date — provenance travels with the fact, not the record.
The wire
Published briefs, searchable via the MCP server or readable as RSS. Every brief names and links the publication that reported the story.

JSON API

Two endpoints, CORS-open, no key required. Both responses include editorial-provenance metadata describing how the data was produced and reviewed.

curl https://avgcxr.in/api/public/policies.json
curl https://avgcxr.in/api/public/entities.json

With an API key, for the higher rate limit:

curl -H "Authorization: Bearer YOUR_KEY" \
  https://avgcxr.in/api/public/policies.json

Markdown variants

Append .md to any brief or policy URL for clean markdown — cheaper to parse and to tokenise than the HTML page. These are alternate representations of the canonical page, served noindex.

curl https://avgcxr.in/policy/karnataka-avgc-xr-policy-2024.md
curl https://avgcxr.in/brief/<slug>.md

MCP server

An MCP (Model Context Protocol) server at https://avgcxr.in/api/mcp — streamable HTTP, read-only. Tools: list_policies (state incentive terms, filterable by jurisdiction), search_wire (published briefs by keyword and segment), lookup_entity (sourced company facts), and get_editorial_policy (process and citation terms).

To add it to a client that reads mcp.json:

{
  "mcpServers": {
    "avgcxr": {
      "type": "http",
      "url": "https://avgcxr.in/api/mcp"
    }
  }
}

Rate limits

Anonymous callers get 120 requests per hour; an API key raises that to 2,000 per hour, and higher on request. Limits are counted per hour in a fixed window and apply across the JSON endpoints and the MCP server together.

Every response carries RateLimit-Limit, RateLimit-Remaining and RateLimit-Reset (Unix seconds). A throttled request returns 429 with Retry-After. Anonymous rate limiting identifies callers by a salted, non-reversible hash — we do not store IP addresses (see privacy).

API keys

Keys are free and exist to raise your rate limit and give us somewhere to send notice before a breaking change — not to gate access. Anonymous use is a first-class path and always will be. Request one at editor@avgcxr.in with what you’re building; we issue by hand.

Send it as Authorization: Bearer <key> or X-API-Key: <key>. An unrecognised or revoked key returns 401 rather than silently dropping you to the anonymous tier. Keys are stored only as hashes — if you lose one, we reissue rather than recover.

Versioning & compatibility

The current revision is 2026-08-30, returned in every response body as apiVersion and in the X-API-Version header.

  • Additive changes ship without notice — new fields, new endpoints, new tools. Parse defensively and ignore fields you don’t recognise.
  • Breaking changes — renaming or removing a field, changing a type, or altering the meaning of an existing value — get 90 days’ notice to every keyed consumer by email, and the old shape stays served for that period.
  • Corrections are not breaking changes. If a policy term was recorded wrongly, the value changes as soon as we know — that is the point of the tracker, and consumers should re-fetch rather than cache indefinitely.

Service commitment

Plainly: this is a free service from a small publication, offered without warranty and with no contractual uptime guarantee. What we do commit to:

  • The endpoints above stay available and free, subject to the versioning terms.
  • Data is served from cache with a short TTL, so a correction reaches consumers the same day.
  • If we ever need to withdraw or meter an endpoint beyond the limits above, keyed consumers get the same 90 days’ notice as a breaking change.
  • Problems, errors in the data, or a limit that doesn’t fit what you’re building: editor@avgcxr.in. A real person answers.

Using the data

Facts are free to cite with attribution to AVGC-XR (avgcxr.in), linking the specific page. Wire briefs summarise reporting by other publications — each names and links the original publisher, and that publisher deserves credit for the underlying story. When citing a policy term, prefer linking the policy page: it carries the primary government source and the archived copy of it.

See also about for how the wire works, and working with AVGC-XR for editorial and commercial terms.