Frontline
Frontline is an AI-native CRM platform that builds and maintains itself. It unifies customer context from WhatsApp, email, and meetings, ships AI agents (Max) that draft replies, proposals, follow-ups and meeting notes, and a Studio for building an AI workforce for sales and support. The Frontline Public API exposes agents, agent-builder flows, automation workflows, CRM objects and rows, tables, tools, intents, AI models, incoming webhooks, account, and billing over REST at https://prod-api.getfrontline.ai/public/v1, authenticated with GENERAL (account) and USER Bearer API keys. Backed by 500 Global.
Real signal across most facets with visible, nameable gaps — the contract exists but is thin, or the portal is good while governance and commercial terms are absent.
API Evangelist profiles Frontline the way a machine reads it — 39 machine-readable artifacts across 33 APIs, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — Frontline scores 49.0/100 (developing), with a separate agent-readiness read of 72/100 (agent native). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance.
How we profile Frontline
Each block below is one kind of artifact we hold for Frontline. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
APIs 33
Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.
Individual APIs this provider publishes, each with its own machine-readable definition.
Frontline Account API
Inspect the identity attached to the current API key
Frontline Agent Builder API
View and manage your AI agents across your account
Frontline Agents API
Agent runtime data: conversations and transcripts
Frontline AI Models API
Discover available AI models for agent configuration
Frontline Billing API
View billing plan details, credits, and renewal information
Frontline Flow Variables API
Manage variables scoped to an agent's flow
Frontline Flows API
View and manage flows associated with your agents
Frontline Incoming Webhooks API
Inbound HTTPS endpoints that external systems can post events to
Frontline Intents API
Manage agent intents and training phrases
Frontline Object activities API
Manual activities (notes, calls, meetings, emails) attached to object rows
Frontline Object aggregations API
Per-view aggregations on objects
Frontline Object export API
Export object data as XLSX or CSV
Frontline Object fields API
Manage columns on an object
Frontline Object files API
Files attached to object rows
Frontline Object options API
Manage tag/select options on object fields
Frontline Object record types API
Categorize records inside an object
Frontline Object relations API
Link and unlink records across objects
Frontline Object rows API
Read and write object records
Frontline Object tasks API
Tasks attached to object rows
Frontline Object views API
Saved view configurations on an object
Frontline Objects API
Manage CRM objects (standard and custom)
Frontline Table activities API
Manual activities (notes, calls, meetings, emails) attached to table rows
Frontline Table aggregations API
Per-view aggregations on tables
Frontline Table export API
Export table data as XLSX or CSV
Frontline Table fields API
Manage columns on a table
Frontline Table files API
Files attached to table rows
Frontline Table options API
Manage tag/select options on table fields
Frontline Table rows API
Read and write table rows
Frontline Table tasks API
Tasks attached to table rows
Frontline Tables API
Manage spreadsheet-style tables
Frontline Tools API
Manage reusable HTTP integrations callable from flows and workflows
Frontline Workflow Variables API
Manage variables scoped to an automation workflow
Frontline Workflows API
View and manage your workflows across your account
Scroll within the panel for all 33 ·
MCP Servers 1
Model Context Protocol servers expose these APIs directly to AI agents. We profile them because agent-native access is the fastest-growing way this provider's capabilities actually get used.
Model Context Protocol servers that expose these APIs to AI agents.
frontline-mcp.yml
MCP SERVERRate Limits 1
Rate limits are the difference between a demo that works and a production integration that doesn't fall over. Publishing them is an operational-transparency signal — and a hard requirement for any agent that plans its own throughput.
Documented rate limits and quota policies.
Frontline Rate Limits
RATE LIMITSSecurity Posture 3
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Agentic Access 1
An x-agentic-access contract marks which operations are safe for an agent to run on its own and which need a human in the loop. It is the difference between an API an agent can use and one it can use safely.
Recommended x-agentic-access execution contracts for AI agents.
Resources
Every other property we hold for Frontline — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Get Started 2
Portal, sign-up, and the first successful call
Documentation 2
Reference material describing how the API behaves
Agent Surfaces 4
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 5
Pagination, idempotency, versioning, errors, and events
Build 2
SDKs, sample code, and the tooling you integrate with
Access & Security 4
Authentication, authorization, and security posture
Operate 2
Status, limits, changes, and where to get help
Commercial 3
Pricing, plans, and the legal terms of use
Company 1
The organization behind the API
Other 1
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/frontline · machine-readable index on apis.io