Install Jentic One Beta

Connect the IndexLinks API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the IndexLinks 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%2Findexlinks.app%2Findexlinks" | 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%2Findexlinks.app%2Findexlinks" | 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 IndexLinks API.

Submit up to 10,000 page urls or a sitemap_url for indexing in one call, with resend to push tracked pages again

Track each page's per-engine status and filter by queued, processing, done, or error

Verify a website's hosted IndexNow key file or install it through a connected Cloudflare zone

Link a Search Console site and read Google rankings over a chosen number of days

GET STARTED

Start building with IndexLinks API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use IndexLinks API for, with concrete tasks.

★ AI agent submitting new pages through Jentic

A developer wants their agent to push freshly published pages for indexing as part of a deploy, without wiring the IndexLinks client by hand. Through Jentic the agent searches for 'submit pages for indexing', loads the submitPages operation with its input schema, and sends the new urls for the website id, with the API key injected at call time. The response counts how many pages were queued, resent, or skipped as duplicates.

Call GET /v1/properties to find the website id, then POST /v1/properties/{id}/submit with urls set to the three newly published blog post URLs and report the queued count

Indexing status monitoring

SEO teams want to know which pages search engines have picked up. GET /v1/properties/{id}/urls lists tracked pages with per-engine status, filterable by status and url_contains, and GET /v1/properties/{id}/urls/{urlId}/status returns one page in detail. Pages with an error status can be resubmitted with resend set to true.

Call GET /v1/properties/{id}/urls with status set to error, then POST /v1/properties/{id}/submit with those urls and resend set to true

Website onboarding and verification

Before submitting, a website needs its IndexNow key file hosted. POST /v1/properties adds the site by name and url, GET /v1/properties/{id}/setup returns the checklist, and POST /v1/properties/{id}/verify checks the hosted key file, or POST /v1/properties/{id}/key-file/install hosts it through a connected Cloudflare zone. Linking Search Console with a site_url enables rankings.

POST /v1/properties with name and url, call POST /v1/properties/{id}/verify, then POST /v1/properties/{id}/search-console with site_url

Key Endpoints

14 endpoints — the indexlinks api submits new and updated pages of a website for search engine and ai crawler indexing and tracks each page's per-engine status.

METHOD

PATH

DESCRIPTION

POST

/v1/properties/{id}/submit

Send pages to every search engine

GET

/v1/properties/{id}/urls

Tracked pages with per-engine status

GET

/v1/properties/{id}/urls/{urlId}/status

One page in detail

GET

/v1/properties

List websites

POST

/v1/properties

Add a website

GET

/v1/properties/{id}/rankings

Google rankings from Search Console

POST

/v1/public/audit

Check how search engines and AI crawlers see a site

POST

/v1/properties/{id}/submit

Send pages to every search engine

GET

/v1/properties/{id}/urls

Tracked pages with per-engine status

GET

/v1/properties/{id}/urls/{urlId}/status

One page in detail

GET

/v1/properties

List websites

POST

/v1/properties

Add a website

GET

/v1/properties/{id}/rankings

Google rankings from Search Console

POST

/v1/public/audit

Check how search engines and AI crawlers see a site

Why Jentic?

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

Setup

Wiring IndexLinks by hand means choosing between a bearer key and the X-API-Key header, verifying an IndexNow key file per website, and batching url submissions per website id. Through Jentic you install once, import IndexLinks from the API Directory, store the key once, and your agent calls it.

Permission scoping

IndexLinks puts the website id in the URL path (/v1/properties/{id}/...), so a rule can pin your agent to one website and the operations you pick for it. You choose the operations it may call, so ones like installing a key file through Cloudflare or saving a Baidu token are not included unless you add them.

Credential isolation

Your IndexLinks API 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 'submit pages for indexing' or 'check indexing status', and Jentic returns the matching IndexLinks operation with its input schema so the agent sends the website id and urls correctly.

FAQs

Specific to using IndexLinks API through Jentic.

What authentication does the IndexLinks API use?

The IndexLinks API accepts an API key (prefixed il_live_) either as a bearer token in the Authorization header or in an X-API-Key header, per its OpenAPI spec. The public site check operations under /v1/public/audit need no credential. Through Jentic the key is stored encrypted by your own Jentic One instance and injected at call time.

Can I submit a whole sitemap with the IndexLinks API?

Yes. POST /v1/properties/{id}/submit accepts either a urls array of up to 10,000 entries or a sitemap_url. Already tracked pages are skipped as duplicates unless you set resend to true, and the response reports queued, resent, duplicates, dropped, and invalid counts.

What are the rate limits for the IndexLinks API?

The OpenAPI spec does not specify rate limits. Check https://indexlinks.app for current limits and plan quotas.

Is there an IndexLinks MCP server?

You don't need an MCP server to give your agent IndexLinks. Jentic connects it directly from the API Directory: import it, store your API key once, and your agent calls the submit, status, and rankings operations it needs, discovered on demand.

Can I limit what my agent is allowed to do with the IndexLinks API?

Yes. As a worked example, allow only the submit and urls listing operations under /v1/properties/{id} for one website id, and the agent can push pages and read their status for that site but cannot add websites, install key files on Cloudflare, or change Search Console links. Every call it makes is logged.

How do I check a page's indexing status through Jentic?

Search Jentic for 'get the indexing status of a page', load the getPageStatus operation, and execute it with the website id and urlId. To run it on your own infrastructure, install Jentic One from its GitHub repo.

Indexlinks App IndexLinks API

AI ReadinessAI-Aware (B-)63/100

See full scorecard

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

For Agents

Submit a website's new or changed pages for indexing, track per-engine status for each page, and read Search Console rankings and a site score.

Use for: Submit the pages in my sitemap for indexing, I want to send these five new blog URLs to search engines, List all pages on my site that errored during submission, Get the indexing status of one page across engines

Not supported: Does not research keywords, build backlinks to order, or edit site content. Use for submitting pages for indexing and tracking their indexing status only.

The IndexLinks API submits new and updated pages of a website for search engine and AI crawler indexing and tracks each page's per-engine status. A client adds a website, verifies its hosted IndexNow key file or installs it through a connected Cloudflare zone, then sends up to 10,000 urls or a sitemap_url in one submit call. It links a Search Console site to read Google rankings, saves a Baidu push token, and returns a website-level score and a setup checklist. A public site check, with no key, reports how search engines and AI crawlers see any URL.

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

100%

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: BSignals: 4

Example Density

How richly the API is illustrated with examples.

100%

Example Validity

Percentage of examples that conform to their schemas.

52%

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

28%

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.

50%

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

58%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the IndexLinks API to your agent

Capabilities

Start building with IndexLinks API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

Indexlinks App IndexLinks API

Jentic AI Readiness Score

IndexLinks 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