canonical: https://jentic.com/apis/aitwire.com/aitwire # AITWIRE API The AITWIRE API scans a site's pages, extracts the content entities it finds, and tracks how AI systems attribute and cite them. It triggers scan runs over a domain, lists the entities discovered with their canonical URL, title, and summary, and returns an authority graph and an AI attribution summary. Governance drift events flag when a tracked entity changes, and webhook endpoints deliver those events to your own systems. You also manage API keys with scopes and read usage for the current billing period. ## For AI agents Scan a site's pages, extract content entities, and track how AI systems attribute and cite them. Trigger scans, read the authority graph and AI attribution summary, monitor governance drift, and manage webhooks and scoped API keys. ## Scope Does not write or publish content, run paid ad campaigns, or host your pages. Use for scanning content entities and tracking their AI attribution, authority, and drift only. ## Capabilities - Trigger a scan over a domain and list its runs with pages scanned and entities found - List and read content entities with their canonical URL, title, summary, and version - Create or update an entity by id to keep the tracked set current - Read the authority graph and the AI attribution summary for tracked entities - Monitor governance drift events and deliver them to webhook endpoints you configure - Manage scoped API keys and read usage for the current billing period ## Use cases ### Agent Monitoring of AI Attribution An agent responsible for a brand's online presence can trigger a scan over the domain, read the AI attribution summary to see how AI systems cite the site's content, and watch governance drift events for changes. Because the attribution summary and authority graph are single reads, the agent can assemble a current picture of AI visibility without crawling pages itself. This supports ongoing monitoring of how a site is represented in AI answers. Example prompt: Trigger a scan of a domain, wait for the run to finish, then read the AI attribution summary and the authority graph and report the top attributed entities. ### Keeping a Tracked Entity Set Current To track specific content, you list the entities a scan discovered and create or update entities by id so the tracked set reflects the real site. Each entity carries a canonical URL, title, summary, hash, and version, so an agent can detect when a page's content has changed by its hash and version. This keeps the authority and attribution views grounded in the current content. Example prompt: List the entities from the latest scan, then create or update an entity by id with its canonical URL, title, and summary. ### Event-Driven Drift Alerts A workflow can create a webhook endpoint, deliver a synthetic test event to confirm it is wired correctly, and then receive governance drift events as tracked entities change. Endpoints can be enabled, disabled, or reconfigured, and deleted when no longer needed. This lets an agent react to drift as it happens rather than polling the drift events list. Example prompt: Create a webhook endpoint for drift events, deliver a synthetic test event to confirm delivery, then enable the endpoint for live events. ## Key endpoints | Method | Path | Description | | --- | --- | --- | | GET | `/entities` | List content entities | | PUT | `/entities/{id}` | Create or update an entity | | POST | `/scans/run` | Trigger a new scan over a domain | | GET | `/authority/graph` | Get the authority graph | | GET | `/attribution/summary` | Get the AI attribution summary | | GET | `/governance/drift/events` | List governance drift events | | POST | `/webhooks` | Create a webhook endpoint | | GET | `/billing/usage` | Get usage for the current billing period | ## Key resources - **Entities** — List, read, and create or update content entities with canonical URL, title, summary, hash, and version - **Scans** — Trigger scan runs over a domain and list past runs with pages scanned and entities found - **Authority and Attribution** — Read the authority graph and the AI attribution summary for tracked entities - **Governance and Webhooks** — List drift events and create, reconfigure, test, or delete webhook endpoints that deliver them - **Keys and Usage** — List and create scoped API keys, list available scopes, and read current billing-period usage ## AI readiness This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use. - **Score:** 60 / 100 - **Maturity:** AI-Aware - **Dimensions:** - Foundational Compliance: 93 / 100 - Developer Experience & Jentic Compatibility: 57 / 100 - AI-Readiness & Agent Experience: 44 / 100 - Agent Usability: 94 / 100 - Security: 55 / 100 - AI Discoverability: 52 / 100 - **View full report:** https://jentic.com/apis/aitwire.com/aitwire/scorecard - **How the score is calculated:** https://docs.jentic.com/reference/api-readiness-framework/overview/ - **More about the dimensions:** https://docs.jentic.com/reference/api-readiness-framework/specification/#dimensional-model-overview ### Score it yourself Every API in the directory is allowlisted, so you can re-score it with no key required. - **Score your own API:** https://jentic.com/scorecard.md - **Scoring CLI agent skill:** https://github.com/jentic/jentic-api-scorecard/blob/main/skills/jentic-api-scorecard/SKILL.md ```sh npx @jentic/api-scorecard-cli score ``` ## Why Jentic - **Setup:** Wiring the AITWIRE API by hand means sending your atwk_ key either as a bearer token or in the X-API-Key header, triggering asynchronous scan runs and polling for completion, and wiring webhook endpoints for drift events. Through Jentic you install once, import it from the API Directory, store the key once, and your agent runs scans and reads attribution without hand-wiring the auth and callbacks. - **Permission scoping:** AITWIRE puts the entity and webhook ids in the URL path (`/entities/{id}`, `/webhooks/{id}`), so a rule can limit your agent to the operations you pick: it can run scans and read the attribution summary and nothing else. You choose the operations it may call, so ones that mint API keys or delete webhooks are not included unless you add them. - **Credential handling:** Your AITWIRE atwk_ key is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context. - **Discovery method:** Agents search Jentic by intent such as 'trigger a scan of my domain' or 'get the AI attribution summary', and Jentic returns the matching AITWIRE operation with its input schema so the agent calls the right endpoint without browsing the reference docs. ## Related APIs - **Ahrefs** — Backlink and search-authority data rather than AI attribution of your own content entities - **Semrush** — Broad SEO and search-visibility analytics instead of entity-level AI attribution and drift monitoring - **NEURONwriter** — Optimises the content itself to pair with AITWIRE's tracking of how AI attributes it ## FAQ ### What authentication does the AITWIRE API use? Per its OpenAPI spec the AITWIRE API accepts your atwk_ key in one of two forms: as a bearer token in the Authorization header, or in the X-API-Key header. Both map to the same scoped API key, which you can list and create through the key operations, and the available scopes are returned by a dedicated scopes read. ### Can I track how AI systems attribute my content with the AITWIRE API? Yes. After a scan run over your domain, the AI attribution summary reports how AI systems attribute the entities it found, and the authority graph shows their standing. You list the discovered entities with their canonical URL, title, and summary, and governance drift events flag when a tracked entity changes. ### What are the rate limits for the AITWIRE API? The spec states tier limits: the Standard tier allows 60 requests per minute, the Pro tier 300 per minute, and the AITWIRE AI tier 1,000 per minute. The billing usage operation reports your consumption for the current period so you can track it against your tier. ### How do I scan a domain with the AITWIRE API through Jentic? Import the AITWIRE API from the Jentic API Directory, then have your agent search by intent such as 'trigger a scan of my domain' and Jentic returns the scan-run operation with its input schema. The agent triggers the scan, lists the run, and reads the attribution summary when it completes. To run it on your own infrastructure, install Jentic One from its GitHub repo. ### Can I limit what my agent is allowed to do with the AITWIRE API? Yes. AITWIRE carries the entity and webhook ids in the URL path, so write a rule that allows only the scan, entity-list, and attribution-read operations, and your agent can monitor attribution but cannot mint API keys or delete webhooks. Add the key and webhook write operations only when the agent genuinely needs them, and every call it makes is logged. ### Is there an AITWIRE MCP server? You don't need an MCP server to give your agent the AITWIRE API. Jentic connects it directly from the API Directory: import it, store your atwk_ key once, and your agent calls the scan, attribution, and webhook operations on demand without loading another server's tool definitions into its context. ### What does a scan run report in the AITWIRE API? A scan run records the domain it covered, its status, how many pages were scanned, and how many entities were found. You list past runs to track scanning over time and read the discovered entities to see exactly what the scan surfaced.