Install Jentic One Beta

Connect the Nautilinks Agent API to your agent

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

Search publisher sites for backlink placements filtered by niche, language, min_tf, max_price, free text, or shelf

List existing insertion articles on a site, with ranking queries and performance data, before choosing the lien_insere format

Place a 1 to 20 item backlink order with site_id, target_url, and anchor_text, or price the same payload with a sandbox key

Check prepaid balance to tell whether an order will settle immediately or needs a human-approved Stripe payment link

GET STARTED

Start building with Nautilinks Agent API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use Nautilinks Agent API for, with concrete tasks.

★ SEO agent that sources and orders backlinks

An SEO agent building links for a client site needs to pick placements and order them without overspending. Through Jentic the agent searches for 'search backlink placements', loads the Nautilinks searchCatalogSites operation with its input schema, and filters by niche, language, and max_price. It checks the prepaid balance, then posts the order; any amount beyond credit comes back as a Stripe link that a human opens. The bearer key is attached by your own Jentic One instance at call time.

Call GET /catalog with niche 'travel', language 'fr', and max_price 200, check GET /balance, then POST /orders with one item giving site_id, target_url 'https://example.com/guide', and anchor_text 'travel guide'

Dry-run orders with a sandbox key

Before letting an agent spend money, a developer tests the full ordering flow with a sandbox key. Nautilinks sandbox keys use the sn_test_ prefix on the same endpoint and validate and price an order payload with no writes and no charges, so the agent's item construction, anchor_type choices, and Idempotency-Key retries can be checked against real pricing first.

Using a sn_test_ key, POST /orders with two items and an Idempotency-Key, then report the priced total returned

Publication tracking with signed webhooks

An agency reporting dashboard needs to know when each backlink is live. Nautilinks returns each link's lifecycle state and published URL on the order, and a webhook subscription for order.published delivers the event with a Nautilinks-Signature HMAC-SHA256 header that the receiver verifies with the secret shown once at creation.

Create a webhook with POST /webhooks for events order.published and order.cancelled, then read GET /orders/{orderId} to list each link's published URL

Closing AI visibility gaps

A brand that wants to be cited in AI answers tracks AI visibility projects in Nautilinks. The plan operation returns uncited opportunities as typed items ready to be reviewed and passed to the order operation, and it never creates a cart, quote, order, or charge on its own.

List projects with GET /ai-visibility/projects, fetch GET /ai-visibility/projects/{projectId}/plan, and present the items for approval before ordering

Key Endpoints

13 endpoints — the nautilinks agent api searches nautilinks publisher sites for backlink placements and orders sponsored articles or links inserted into existing articles.

METHOD

PATH

DESCRIPTION

GET

/catalog

Search backlink placements

GET

/catalog/{siteId}/articles

List insertion articles on a site

POST

/orders

Create or simulate an order

GET

/orders/{orderId}

Get order and placement status

GET

/balance

Get prepaid balance

GET

/quotes/{quoteId}

Get quote payment status

POST

/webhooks

Create a signed webhook subscription

GET

/ai-visibility/projects/{projectId}/plan

Get an AI visibility plan

GET

/catalog

Search backlink placements

GET

/catalog/{siteId}/articles

List insertion articles on a site

POST

/orders

Create or simulate an order

GET

/orders/{orderId}

Get order and placement status

GET

/balance

Get prepaid balance

GET

/quotes/{quoteId}

Get quote payment status

POST

/webhooks

Create a signed webhook subscription

GET

/ai-visibility/projects/{projectId}/plan

Get an AI visibility plan

Why Jentic?

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

Setup

Wiring Nautilinks by hand means managing separate sn_live_ and sn_test_ bearer keys, sending an Idempotency-Key on order retries, and handling the split between prepaid credit and Stripe payment links. Through Jentic you install once, import Nautilinks from the API Directory, store the key once, and your agent calls it.

Permission scoping

Nautilinks puts the site id, order id, and webhook id in the URL path, so a rule can hold your agent to the operations you pick, such as reading one order by id. You choose which it may call, so spending ones like order creation or destructive ones like webhook revocation are not included unless you add them.

Credential isolation

Your Nautilinks 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 'search backlink placements' or 'track a backlink order', and Jentic returns the matching Nautilinks operation with its input schema so the agent builds a valid order item.

FAQs

Specific to using Nautilinks Agent API through Jentic.

What authentication does the Nautilinks Agent API use?

Per its OpenAPI spec, the Nautilinks Agent API uses HTTP bearer authentication with a key created in the Nautilinks member area: live keys start with sn_live_ and sandbox keys with sn_test_, each followed by 40 hex characters. The key goes in the Authorization header, never in a URL. Through Jentic the key is stored encrypted by your own instance and attached per call.

Can I test a backlink order without being charged?

Yes. Send the same POST /orders payload with a sandbox key (prefix sn_test_). Nautilinks validates and prices the order without writing it or charging anything. With a live key, prepaid credit is spent immediately and any remainder is returned as a Stripe payment URL that a human must open.

What are the rate limits for the Nautilinks Agent API?

The OpenAPI spec does not state rate limits. It does limit order size to 1 to 20 items per request and asks you to reuse the same Idempotency-Key after a timeout so a retried order is not duplicated. Check https://nautilinks.co for current limits.

Is there a Nautilinks MCP server?

You don't need an MCP server to give your agent Nautilinks. Jentic connects it directly from the API Directory: import it, store your sn_live_ or sn_test_ key once, and your agent calls the search, order, and tracking operations it needs.

How do I order a backlink with the Nautilinks Agent API through Jentic?

Import Nautilinks from the API Directory in your Jentic One instance and store your key. Your agent searches for 'order a backlink', loads POST /orders, and sends items with site_id, target_url, and anchor_text, adding article_id when the format is lien_insere. 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 Nautilinks Agent API?

Yes. Write a rule that allows only GET /catalog, GET /catalog/{siteId}, and GET /balance, and the agent can research placements and check credit but cannot place an order or revoke a webhook. Add POST /orders later when you want it to buy, and every call it makes is logged.

Nautilinks Agent API

AI ReadinessAI-Aware (B+)69/100

See full scorecard

Official vendor OpenAPI document · agent-readyMarketingSeo Sembearer13 EndpointsREST

For Agents

Search backlink placements by niche, language, trust flow, and price, simulate or place backlink orders, and track each link through to publication.

Use for: Find backlink placements in the travel niche under 200 euros, List French-language publisher sites with a trust flow above 20, I want to simulate a backlink order before spending credit, Check whether my prepaid balance covers this order

Not supported: Does not write the client's own site content, run keyword rank tracking, or manage paid search ads. Use for finding, ordering, and tracking Nautilinks backlink placements only.

The Nautilinks Agent API searches Nautilinks publisher sites for backlink placements and orders sponsored articles or links inserted into existing articles. Sites can be filtered by niche, language, minimum trust flow, maximum price, and the Plancton, Corail, or Nautilus fixed-price shelf, and an order of 1 to 20 items is paid from prepaid credit or handed to a human as a Stripe payment link for any remainder. Orders report each link's lifecycle up to the published URL, signed webhooks announce acceptance, publication, or cancellation, and a sandbox key with the sn_test_ prefix prices an order without creating or charging it.

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: A-Signals: 4

Example Density

How richly the API is illustrated with examples.

100%

Example Validity

Percentage of examples that conform to their schemas.

100%

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: D+Signals: 4

40%

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.

52%

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: B-Signals: 1

60%

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: A-Signals: 1

79%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the Nautilinks Agent API to your agent

Capabilities

Start building with Nautilinks Agent API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

Nautilinks Agent API

Jentic AI Readiness Score

Nautilinks Agent 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