Install Jentic One Beta

Connect the AITWIRE API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the AITWIRE API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Faitwire.com%2Faitwire" | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Faitwire.com%2Faitwire" | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with AITWIRE API.

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

GET STARTED

Start building with AITWIRE API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use AITWIRE API for, with concrete tasks.

★ 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.

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.

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.

Create a webhook endpoint for drift events, deliver a synthetic test event to confirm delivery, then enable the endpoint for live events.

Key Endpoints

17 endpoints — the aitwire api scans a site's pages, extracts the content entities it finds, and tracks how ai systems attribute and cite them.

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

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

Why Jentic?

What agents get from Jentic-routed access to this vendor.

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 isolation

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.

Intent-based discovery

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.

FAQs

Specific to using AITWIRE API through Jentic.

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.

AITWIRE API

AI ReadinessAI-Aware (B-)60/100

See full scorecard

Official vendor OpenAPI document · agent-readyMarketingSeo Sembearer, apikey17 EndpointsREST

For 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.

Use for: Trigger a scan of my domain, List the entities found in the latest scan, Get the AI attribution summary for my site, Show me the authority graph

Not supported: 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.

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.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: A+Signals: 4

98%

Lint Results

Aggregated quality score from linter diagnostics, weighted by severity.

100%

Resolution Completeness

Percentage of `$ref` references that resolve successfully.

100%

Specification Validity

Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).

75%

Structural Integrity

Structural correctness score based on schema issues using logarithmic dampening.

Developer Experience & Jentic Compatibility

Clarity, completeness, and ingestion readiness for developers and tooling.

Grade: C+Signals: 4

Example Density

How richly the API is illustrated with examples.

100%

Example Validity

Percentage of examples that conform to their schemas.

29%

Response Coverage

Percentage of operations with complete response definitions (success, client error, server error).

100%

Tooling Readiness

Health of API ingestion, bundling, and resolution within Jentic pipelines.

AI-Readiness & Agent Experience

Semantic breadth, depth, and agent comprehension for AI systems.

Grade: DSignals: 4

21%

Description Coverage

Coverage of descriptions across API elements.

Error Standardization

Coverage of RFC 9457 Problem Details for error responses.

100%

OperationId Quality

Coverage, uniqueness, and casing consistency of operationIds for AI inference.

55%

Summary Coverage

Coverage of summaries across operations/tags/info.

Agent Usability

Functional utility, complexity comfort, and AI orchestration readiness.

Grade: A+Signals: 1

94%

Complexity Comfort

Agent comfort level based on API operational and structural complexity.

Security

Trust, risk posture, and security compliance.

Grade: CSignals: 1

55%

Authentication Strength

Average quality of security schemes based on authentication method strength (weakest link for OAuth2).

AI Discoverability

Findability, semantic richness, and reasoning readiness.

Grade: C-Signals: 1

52%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the AITWIRE API to your agent

Capabilities

Start building with AITWIRE API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

AITWIRE API

Jentic AI Readiness Score

AITWIRE API

Foundational Compliance

Lint Results

Resolution Completeness

Specification Validity

Structural Integrity

Developer Experience & Jentic Compatibility

Example Density

Example Validity

Response Coverage

Tooling Readiness

AI-Readiness & Agent Experience

Description Coverage

Error Standardization

OperationId Quality

Summary Coverage

Agent Usability

Complexity Comfort

Security

Authentication Strength

AI Discoverability

Descriptive Richness