Install Jentic One Beta

Connect the Lane Public API to your agent

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

Create feedback with a title and description, linked to a company by company_domain or company_name and to a person by customer_email

Backdate feedback with created_at so trends place it on the day it was given

Queue feedback with a description for Lane's AI insight extraction

List signals in every status, most recently updated first, with priorityScore, customerCount, insightCount, and totalRevenue

GET STARTED

Start building with Lane Public API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use Lane Public API for, with concrete tasks.

★ Routing Support Feedback into Lane

Feedback scattered across support tickets, sales calls, and chat is pushed into Lane as it arrives. The agent sends a title and description with the company_domain and customer_email, so Lane links the feedback to the right account and person and queues it for insight extraction. Values Lane cannot use, such as a personal email domain, are skipped and reported in warnings rather than failing the call.

Call POST /records/feedback with title 'CSV export is too slow', description 'Exporting a large report times out', company_domain 'acme.com', and customer_email 'jane@acme.com'

Revenue-Weighted Priority Review

Product teams want to know which problems matter most to paying customers. The agent pulls signals with a min_priority_score threshold and ranks them by priorityScore, customerCount, and totalRevenue to brief the team on the top issues. Each signal has a stable id, so a scheduled agent can tell new signals from ones it already reported.

Call GET /records/signals with min_priority_score 70 and limit 20, then summarise each signal's name, priorityScore, customerCount, and totalRevenue

Backfilling Historical Feedback

When a team adopts Lane, older feedback should land on the dates it was given. The agent replays exported feedback with created_at set to the original ISO 8601 date, so Lane's trends and lists show it in the right period instead of on the import day.

For each exported row, call POST /records/feedback with title, description, customer_email, and created_at set to the row's original date such as '2026-03-04'

AI Agent Feedback Capture via Jentic

A support or sales agent logs feedback through Jentic without holding the Lane key. It searches by intent, receives the feedback operation with its input schema, and executes with the key injected at run time, so capturing a customer's request becomes one step at the end of every conversation.

Search Jentic for 'log customer feedback in Lane', load the POST /records/feedback schema, and execute it with the title, description, and customer_email from the conversation

Key Endpoints

3 endpoints — the lane public api sends customer feedback into lane and reads back the signals lane builds from it.

METHOD

PATH

DESCRIPTION

POST

/records/feedback

Create feedback

GET

/records/signals

List signals

GET

/records/verify

Verify connection

POST

/records/feedback

Create feedback

GET

/records/signals

List signals

GET

/records/verify

Verify connection

Why Jentic?

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

Setup

Wiring Lane by hand means choosing between its x-api-key header and bearer forms, resolving which company each piece of feedback belongs to, and handling the warnings Lane returns for values it skips. Through Jentic you install once, import Lane from the API Directory, store the key once, and your agent calls it.

Permission scoping

Lane carries the company and person inside the request body, so rules bound which operations your agent may call, not which customer it writes about. Limit the agent to the operations it needs, such as creating feedback or reading signals.

Credential isolation

Your Lane 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 'log customer feedback' or 'list high priority signals', and Jentic returns the matching Lane operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using Lane Public API through Jentic.

What authentication does the Lane Public API use?

Per its OpenAPI spec, the Lane Public API accepts your Lane API key two ways: in the x-api-key header (the ApiKeyHeader scheme) or as Authorization: Bearer (the BearerAuth scheme). Requests are scoped to the workspace that owns the key, and GET /records/verify confirms a key and returns that workspace. Through Jentic the key is stored encrypted by your own Jentic One instance and injected at execution time.

How does the Lane Public API decide which company feedback belongs to?

It uses the first that applies: company_domain, then an exact company_name match, then the company of the person in customer_email. A domain is the most reliable, and a URL works too. Values Lane cannot use, such as a personal email domain, are skipped and listed in the response warnings, and the feedback is still created.

What are the rate limits for the Lane Public API?

The OpenAPI spec does not specify rate limits. Check https://docs.laneapp.co for current limits. The signals list is designed for polling, and limit caps how many signals each call returns.

How do I log customer feedback through Jentic with the Lane Public API?

Search Jentic for 'log customer feedback in Lane' and it returns the feedback operation with its input schema. Execute POST /records/feedback with a title (required) and any of description, customer_email, customer_name, company_domain, company_name, created_at, and source. To run it on your own infrastructure, install Jentic One from its GitHub repo.

Is there a Lane MCP server?

You don't need an MCP server to give your agent the Lane Public API. Jentic connects it directly from the API Directory: import it, store your credential once, and your agent calls it. Operations are discovered by intent on demand, so no extra server's tool definitions are loaded into the agent's context.

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

Yes. A reporting agent can be allowed only the signals list and the verify call, so it reads priorities but never writes feedback. A support agent can be allowed only feedback creation, so it logs what customers say without seeing revenue-weighted signals, and every call it makes is logged by your own instance.

Laneapp Lane Public API

AI ReadinessFoundational (D+)49/100

See full scorecard

Official vendor OpenAPI document · agent-readyCRMCustomer SuccessapiKey, bearer3 EndpointsREST

For Agents

Log customer feedback in Lane against the right company and person, and pull the prioritized signals Lane derives from it, filtered by a minimum priority score.

Use for: Log this customer's complaint about slow CSV exports in Lane, Add feedback from jane@acme.com about the pricing page, List the signals with a priority score of 70 or more, Get the top customer pain points by revenue

Not supported: Does not handle support ticketing, customer messaging, or editing and closing signals. Use for sending customer feedback to Lane and reading its prioritized signals only.

The Lane Public API sends customer feedback into Lane and reads back the signals Lane builds from it. Each piece of feedback can be linked to the company it came from by company_domain or company_name and to the person by customer_email, and feedback with a description is queued for AI insight extraction. Signals come back with a priorityScore, the number of customers and insights behind them, and the total revenue they represent, ready for polling from an automation.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: A-Signals: 4

92%

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

15%

Example Density

How richly the API is illustrated with examples.

100%

Example Validity

Percentage of examples that conform to their schemas.

50%

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

48%

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.

56%

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

50%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the Lane Public API to your agent

Capabilities

Start building with Lane Public API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

Laneapp Lane Public API

Jentic AI Readiness Score

Lane Public 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