Install Jentic One Beta

Connect the Arbo API to your agent

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

Add a page to a project's sitemap tree

Update a single page or bulk-update many pages at once

Import a full sitemap tree into a project in one call

List version snapshots of a project's sitemap

Read a project's review with per-page status, version, and Figma link

GET STARTED

Start building with Arbo API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use Arbo API for, with concrete tasks.

★ Agent-Built Sitemaps

An AI agent planning a website can call the Arbo API through Jentic to turn a page outline into a visual sitemap, adding each page to the project tree. The agent builds the structure without the developer wiring the bearer auth or the project and node paths by hand, and it can bulk-update pages as the plan changes. Jentic returns the matching operation and its input schema so the agent edits the sitemap inline.

Add a page to a project's sitemap for each section of a site outline and return the resulting tree

Bulk Sitemap Import and Editing

A tool migrating or restructuring a site can import a whole sitemap tree in one call rather than adding pages one by one, then bulk-update many pages together. Arbo imports a full tree, updates multiple pages in a single bulk request, and exposes an async job to poll while a large import completes.

Import a sitemap tree into a project, then bulk-update the labels on several pages and poll the import job until it finishes

Review Status and Comments

A design handoff can track where each page stands by reading its review status, version, and linked Figma design, and the comments reviewers pinned to a version and breakpoint. Arbo returns the per-page review and its comments, so a workflow can surface which pages are approved and which still have open feedback.

Read a project's review and list the pages that still have open review comments

Key Endpoints

13 endpoints — the arbo api builds and manages a project's visual sitemap, the tree of pages that describes a website's structure.

METHOD

PATH

DESCRIPTION

POST

/api/v1/projects/{id}/nodes

Add a page to the sitemap

GET

/api/v1/projects/{id}/nodes

List all active pages

PUT

/api/v1/projects/{id}/nodes/{nid}

Update a page

PATCH

/api/v1/projects/{id}/nodes/bulk

Update multiple pages at once

POST

/api/v1/projects/{id}/import

Import a full sitemap tree

GET

/api/v1/projects/{id}/history

List version snapshots

GET

/api/v1/projects/{id}/review

Review status, version, and Figma link per page

POST

/api/v1/projects/{id}/nodes

Add a page to the sitemap

GET

/api/v1/projects/{id}/nodes

List all active pages

PUT

/api/v1/projects/{id}/nodes/{nid}

Update a page

PATCH

/api/v1/projects/{id}/nodes/bulk

Update multiple pages at once

POST

/api/v1/projects/{id}/import

Import a full sitemap tree

GET

/api/v1/projects/{id}/history

List version snapshots

GET

/api/v1/projects/{id}/review

Review status, version, and Figma link per page

Why Jentic?

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

Setup

Wiring Arbo by hand means handling its bearer token, threading the project and node ids through each path, and polling the async job endpoint while a large import completes. Through Jentic you install once, import Arbo from the API Directory, store the token once, and your agent calls it.

Permission scoping

Arbo puts the project id in the URL path, so a rule can pin your agent to one project and the operations you pick on it. You choose which operations it may call, so page removal is not included unless you add it.

Credential isolation

Your Arbo token 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 'add a page to a sitemap' or 'import a sitemap tree', and Jentic returns the matching Arbo operation with its input schema so the agent calls the right endpoint directly.

FAQs

Specific to using Arbo API through Jentic.

What authentication does the Arbo API use?

The Arbo API authenticates with a bearer token on its project operations, per its OpenAPI spec, while a health-check operation is open. Through Jentic the token is stored once, encrypted, by your own Jentic One instance and injected at call time, so it never reaches the agent's prompt or logs.

Is there an Arbo MCP server?

You don't need an MCP server to give your agent the Arbo API. Jentic connects it directly from the API Directory: import it, store your token once, and your agent can build and edit sitemaps straight away.

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

Yes. Arbo puts the project id in the URL path, so a rule can bound your agent to one project and the operations you pick on it. Allow it to add pages and read reviews but leave page removal out unless you add it, and every call it makes is logged.

Can I import a full sitemap into a project with the Arbo API?

Yes. The import operation takes a whole sitemap tree and loads it into a project in one call, and an async job operation lets an agent poll until a large import finishes rather than adding pages individually.

What are the rate limits for the Arbo API?

The OpenAPI spec does not publish a numeric rate limit for the Arbo API. Check the Arbo documentation for the current limits on your plan.

How do I add a page to a sitemap with the Arbo API through Jentic?

Search Jentic for an intent like 'add a page to a sitemap' and it returns the Arbo add-page operation with its input schema, so your agent sends the page details and reads back the updated tree. To run it on your own infrastructure, install Jentic One from its GitHub repo.

Getarbo Arbo API

AI ReadinessFoundational (C+)59/100

See full scorecard

Official vendor OpenAPI document · agent-readyProductivityCollaborationbearer13 EndpointsREST

For Agents

Build and manage a project's visual sitemap tree: add, update, bulk-edit, and import pages, list version snapshots, and read per-page review status and comments. Authenticates with a bearer token.

Use for: Add a page to a project's sitemap, Update several pages in a sitemap at once, Import a full sitemap tree into a project, List the version snapshots of a sitemap

Not supported: Does not handle website hosting, content publishing, or SEO analytics. Use for building and managing visual sitemaps only.

The Arbo API builds and manages a project's visual sitemap, the tree of pages that describes a website's structure. An agent reads a project and its pages, adds a page, updates one page or many at once in bulk, and imports a whole sitemap tree in a single call. It lists version snapshots of the sitemap, polls async jobs, and reads a review that carries each page's status, version, and Figma link along with the comments pinned to a version and breakpoint. Responses are JSON and authentication is a bearer token.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

100

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

Example Density

How richly the API is illustrated with examples.

100%

Example Validity

Percentage of examples that conform to their schemas.

31%

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

23%

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.

54%

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: FSignals: 1

39%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the Arbo API to your agent

Capabilities

Start building with Arbo API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

Getarbo Arbo API

Jentic AI Readiness Score

Arbo 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