Install Jentic One Beta

Connect the Lindo Unified API to your agent

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

Start a website-creation workflow from a prompt, optionally scheduled with schedule_at and assigned to a client

Edit an existing website or create blog posts with an AI prompt and poll the workflow status by workflow_id

Create, update, unpublish, or fetch the HTML of individual pages and blogs on a website

Add or remove a custom domain and update a website's settings such as theme, fonts, language, and robots

GET STARTED

Start building with Lindo Unified API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use Lindo Unified API for, with concrete tasks.

★ Agent-built client websites through Jentic

An agency's AI agent can turn a client brief into a live site: it starts a website-creation workflow from a prompt with the client's business details, assigns it to the client, polls the workflow by workflow_id, and adds the client's custom domain when the site is ready. Through Jentic the agent finds each Lindo operation by intent and loads its schema, so the developer does not hand-wire the workflow and polling calls.

Start a website-creation workflow with the prompt 'Create a modern landing page for a coffee shop called Bean There with a warm color scheme' and a client email, poll its status by workflow_id until it finishes, then add the domain beanthere.com to the new website_id.

Batch blog content production

Content teams can queue up to 25 AI blog posts on one website in a single batch request, each with its own workflow_id, and check up to 25 blog workflows at once with the batch status operation instead of polling each one.

Create a batch of five blog posts on a website from five prompts, then check the status of all five workflow_ids in one batch status call.

AI visibility reporting

Beyond visitor analytics, Lindo reports how AI systems see a site. Per website it returns AI bot crawls, AI platform referrals, top cited pages, and a time series of both signals; across the workspace it shows how often AI crawlers such as GPTBot and ClaudeBot fetch your pages and how many visitors arrive from AI chat platforms. Both take optional from and to dates, so agencies can include the figures in client reports.

Fetch the AI visibility analytics for a website_id with from and to set to the last 30 days and list the top cited pages.

Agency client and credit management

Agencies running many client sites can create workspace clients with website and credit limits, send them a magic link to sign in, suspend or update them, and allocate credits from the workspace pool to a client by credit type.

Create a workspace client with email 'owner@beanthere.com' and a website_limit of 2, then allocate 100 credits of credit_type 'purchased' to that client_id.

Key Endpoints

62 endpoints — the lindo unified api builds and runs ai-generated websites for agencies and their clients: it starts website-creation, website-edit, and blog-creation workflows from a text prompt, in batches of up to 25, and reports each workflow's status by workflow_id.

METHOD

PATH

DESCRIPTION

POST

/v1/ai/workspace/website

Create a website with an AI prompt

GET

/v1/ai/workspace/website/status/{workflow_id}

Check a website-creation workflow

POST

/v1/ai/workspace/website/{website_id}/blog

Create a blog post with an AI prompt

POST

/v1/workspace/website/{website_id}/pages/create

Create a page

POST

/v1/workspace/website/{website_id}/domain

Add a custom domain

GET

/v1/workspace/website/{website_id}/analytics/ai-visibility

Get AI visibility analytics

POST

/v1/workspace/client/create

Create a workspace client

POST

/v1/ai/credits/client/allocate

Allocate credits to a client

POST

/v1/ai/workspace/website

Create a website with an AI prompt

GET

/v1/ai/workspace/website/status/{workflow_id}

Check a website-creation workflow

POST

/v1/ai/workspace/website/{website_id}/blog

Create a blog post with an AI prompt

POST

/v1/workspace/website/{website_id}/pages/create

Create a page

POST

/v1/workspace/website/{website_id}/domain

Add a custom domain

GET

/v1/workspace/website/{website_id}/analytics/ai-visibility

Get AI visibility analytics

POST

/v1/workspace/client/create

Create a workspace client

POST

Why Jentic?

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

Setup

Wiring Lindo by hand means attaching the lindo_sk_ bearer key, starting asynchronous AI workflows, and polling separate status routes for websites, edits, and blogs. Through Jentic you install once, import Lindo from the API Directory, store the key once, and your agent calls it.

Permission scoping

Lindo puts the website id in the URL path (/v1/workspace/website/{website_id}/...), so a rule can pin your agent to one website and the operations you pick on it. You choose the operations it may call, so destructive ones like deleting a website or removing its custom domain are not included unless you add them.

Credential isolation

Your Lindo 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 'create a website from a prompt' or 'write a blog post', and Jentic returns the matching Lindo operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using Lindo Unified API through Jentic.

What authentication does the Lindo Unified API use?

Per its OpenAPI spec the Lindo Unified API uses HTTP bearer authentication: you send your Lindo API key, which starts with lindo_sk_, in the Authorization header. Through Jentic the key is stored encrypted by your own Jentic One instance and injected at request time.

Is there a Lindo MCP server?

You don't need an MCP server to give your agent the Lindo Unified API. Jentic connects it directly from the API Directory: import it, store your credential once, and your agent discovers website, blog, and analytics operations on demand instead of loading a large tool list into its context.

Can I create a website from a prompt with the Lindo API?

Yes. The AI website creation operation takes a prompt of at least 10 characters describing the site, plus optional schedule_at for a future run and a client to assign it to, and returns a workflow_id. Poll the website-creation status operation with that id until the workflow finishes. A batch version starts up to 25 sites in one request.

What are the rate limits for the Lindo Unified API?

The OpenAPI spec does not specify rate limits. AI workflows draw on workspace credits, which you can read with the credits operation. Check https://lindo.ai for current limits on your plan.

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

Yes. For example, write a rule that allows only the AI blog creation, blog status, and blog read operations under /v1/ai/workspace/website/site_123/ and /v1/workspace/website/site_123/blogs/, so the agent can draft posts for that one site while deleting websites, removing domains, and allocating credits stay outside its reach. Every call it makes is logged.

How do I add a custom domain to a Lindo website through Jentic?

Search Jentic for 'add a custom domain to a website', load the operation, and pass the website_id in the path and the domain in the body. Jentic injects your lindo_sk_ key at call time. To run it on your own infrastructure, install Jentic One from its GitHub repo.

What does Lindo AI visibility analytics measure?

Per website, the AI visibility operation returns AI bot crawls, AI platform referrals, top cited pages, and a time series of both signals. The workspace-level version reports how often AI crawlers such as GPTBot, ClaudeBot, and PerplexityBot fetch your pages and how many visitors arrive from AI chat platforms. Both accept optional from and to dates.

Lindo Unified API

AI ReadinessFoundational (C)54/100

See full scorecard

Official vendor OpenAPI document · agent-readyMarketingContent Managementbearer62 EndpointsREST

For Agents

Generate websites and blog posts from prompts, edit pages and blogs, attach custom domains, manage agency clients and credits, and read traffic and AI visibility analytics.

Use for: I need to create a landing page for a coffee shop from a prompt, Check the status of my website-creation workflow, Write three blog posts on this website with AI, Add a custom domain to this website

Not supported: Does not register domain names, send email campaigns, or host code repositories. Use for generating, editing, and managing AI-built websites and blogs only.

The Lindo Unified API builds and runs AI-generated websites for agencies and their clients: it starts website-creation, website-edit, and blog-creation workflows from a text prompt, in batches of up to 25, and reports each workflow's status by workflow_id. It also edits pages and blogs directly, uploads media, sets custom domains, sells products on a site, and manages workspace clients, team members, and credit allocations. Analytics cover visitor traffic and AI visibility, including AI bot crawls, AI platform referrals, and top cited pages.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: A-Signals: 4

94%

Lint Results

Aggregated quality score from linter diagnostics, weighted by severity.

100%

Resolution Completeness

Percentage of `$ref` references that resolve successfully.

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

34%

Example Density

How richly the API is illustrated with examples.

100%

Example Validity

Percentage of examples that conform to their schemas.

70%

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

54%

Description Coverage

Coverage of descriptions across API elements.

Error Standardization

Coverage of RFC 9457 Problem Details for error responses.

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

92%

Complexity Comfort

Agent comfort level based on API operational and structural complexity.

Security

Trust, risk posture, and security compliance.

Grade: A-Signals: 1

75%

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

84%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the Lindo Unified API to your agent

Capabilities

Start building with Lindo Unified API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

Lindo Unified API

Jentic AI Readiness Score

Lindo Unified 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