canonical: https://jentic.com/apis/laneapp.co/laneapp # Laneapp Lane Public API 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. ## For AI 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. ## Scope 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. ## Capabilities - 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 - Narrow the signal list server-side with min_priority_score and cap it with limit - Verify an API key and read the workspace it belongs to ## Use cases ### 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. Example prompt: 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. Example prompt: 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. Example prompt: 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. Example prompt: 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 | Method | Path | Description | | --- | --- | --- | | POST | `/records/feedback` | Create feedback | | GET | `/records/signals` | List signals | | GET | `/records/verify` | Verify connection | ## Key resources - **Feedback** — Create feedback linked to a company and person, optionally backdated and queued for insight extraction - **Signals** — List prioritized signals with scores, customer and insight counts, and revenue - **Connection** — Verify the API key and return the owning workspace ## AI readiness This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use. - **Score:** 49 / 100 - **Maturity:** Foundational - **Dimensions:** - Foundational Compliance: 73 / 100 - Developer Experience & Jentic Compatibility: 66 / 100 - AI-Readiness & Agent Experience: 26 / 100 - Agent Usability: 94 / 100 - Security: 55 / 100 - AI Discoverability: 50 / 100 - **View full report:** https://jentic.com/apis/laneapp.co/laneapp/scorecard - **How the score is calculated:** https://docs.jentic.com/reference/api-readiness-framework/overview/ - **More about the dimensions:** https://docs.jentic.com/reference/api-readiness-framework/specification/#dimensional-model-overview ### Score it yourself Every API in the directory is allowlisted, so you can re-score it with no key required. - **Score your own API:** https://jentic.com/scorecard.md - **Scoring CLI agent skill:** https://github.com/jentic/jentic-api-scorecard/blob/main/skills/jentic-api-scorecard/SKILL.md ```sh npx @jentic/api-scorecard-cli score ``` ## Why Jentic - **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 handling:** 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. - **Discovery method:** 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. ## Related APIs - **Canny API** — Feature request boards, votes, and roadmaps - **Featurebase API** — Feedback boards and changelogs - **Intercom API** — Customer conversations and support inbox - **Zendesk API** — Support tickets and help desk ## FAQ ### 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.