API access: a census of 143 listings

A documented public API spans both workers, with webhooks and bi-directional data flow so another system can trigger outbound, inbound and meeting booking.

Source retrieved 2026-09-23

Ada publishes REST APIs, webhooks, SDKs and an OpenAPI spec with rotatable keys, but the Data Export API may fall outside a given subscription package.

Source retrieved 2026-10-03

Programmatic access is local and MCP-shaped rather than an HTTP API: a reply MCP tool, local WebSocket control ports, and --json output on doctor and budget, with no public web API.

Source retrieved 2026-10-03

APIs live inside what it builds for you, as typed tool contracts on delivered task agents; Agentix publishes no product API of its own.

Source retrieved 2026-09-09

The product is itself a programmatic surface: typed npm packages plus named CLI functions you import, so every subcommand is drivable from your own code.

Source retrieved 2026-09-09

AgentOS exposes REST and SSE endpoints for runs, sessions, memory, traces, evals and schedules, with an OpenAPI spec.

Source retrieved 2026-09-02

The API is for connecting your systems into Aide, not a published API for driving Aide from your stack: custom back-office systems connect via API or MCP, and no developer documentation or endpoint reference is published on the site.

Source retrieved 2026-09-23

Programmatic access is real but takes the form of a hosted MCP server and a CLI; no public REST API reference is published for driving Loadout from your own code.

Source retrieved 2026-10-03

You can drive it from your own stack via the CLI or a Python Coder object, but the vendor states the Python API is neither supported nor documented and may break between releases.

Source retrieved 2026-09-30

A documented API surface exists for driving the product from your own stack: conversation and workflow APIs for custom front ends, plus ingestion APIs and listener channels that let external systems trigger agent workflows.

Source retrieved 2026-09-24

A documented REST API covers people search, sequences, lead lists, contacts, calls and webhooks with bearer-token auth, and the vendor states it costs nothing extra on top of the subscription.

Source retrieved 2026-09-10

Headless runs return a JSON envelope or streaming NDJSON with token usage and tool calls, accept a JSON schema, and take prompts on stdin; note the terms forbid third-party clients using Antigravity OAuth.

Source retrieved 2026-09-10

Beyond the proxied APIs themselves, account management is programmatic: documented REST endpoints subscribe, upgrade, downgrade and cancel plans with the same key header.

Source retrieved 2026-10-03

A documented REST API is included on every paid plan and on pay-as-you-go, sharing one account and credit balance with the app, with rate limits rising by tier.

Source retrieved 2026-09-26

Only inbound: a per-campaign webhook endpoint with its own API key lets you push leads in from any HTTP client, and webhooks appear only from the Employee plan upward. No general read or write REST API is documented anywhere in the help centre.

Source retrieved 2026-09-10

A documented REST API under /api/v1/ configures the platform and reads back calls, recordings, transcripts and campaigns, with OAuth 2.0 client-credentials authentication.

Source retrieved 2026-09-24

Auggie TypeScript/Python SDKs drive the agent from your own code; the Analytics API is Enterprise-only preview.

Source retrieved 2026-09-02

It is itself a programming interface you import into your own stack, with layered Python packages for core runtime, agent teams and extensions.

Source retrieved 2026-09-19

You can drive conversations from your own stack through a per-source Lead Reply API plus an outbound REST webhook, but the vendor publishes no endpoint reference, base URL or general-purpose API for agents, calls or reporting.

Source retrieved 2026-09-11

They build authenticated API connections from the agent into your systems, so integration is a deliverable; there is no Bitsclan API or developer documentation letting you drive the vendor yourself.

Source retrieved 2026-09-11

A documented public REST API covers calls, pathways, knowledge bases, numbers and webhooks on every plan.

Source retrieved 2026-09-11

Public Chat, Admin, Files, Tables and Runtime APIs at api.botpress.cloud, authenticated with a bearer token; no row in the plan comparison table gates API access.

Source retrieved 2026-09-02

The terms commit the vendor to providing an API alongside the web interface, and a public Postman collection at api.botsify.com documents bot API keys and message endpoints.

Source retrieved 2026-09-13

REST API and Node/Python SDKs for sessions, agents, contexts, search, fetch and Functions on every plan.

Source retrieved 2026-09-02

REST and WebSocket APIs cover TTS, STT and agent management, with official Python and JS SDKs.

Source retrieved 2026-09-02

The product is itself a library for your stack, in Python or TypeScript, with a CLI fallback for other languages.

Source retrieved 2026-09-02

The Agent SDK exposes the same agent loop as a Python or TypeScript library, and claude -p with JSON output drives it from any language.

Source retrieved 2026-09-02

Two documented APIs plus an SDK: an OpenAI-compatible chat completions endpoint for inference, a REST admin API for orgs and keys, and npm packages that embed the agent loop itself.

Source retrieved 2026-09-12

The REST API for metrics, users, roles, audit logs and security findings is Enterprise-only; lower tiers get an agentic API key for headless CLI review authentication.

Source retrieved 2026-09-15

TypeScript and Python SDKs plus an app-server protocol drive local Codex threads programmatically.

Source retrieved 2026-09-02

The plan table marks API access as No on Free and Starter and full only from Pro at $29, while the vendor's own API FAQ says the API works on every plan including free — a contradiction a buyer should check before subscribing.

Source retrieved 2026-09-28

Developers can drive the embedded assistant from their own page through widget functions that pass context, but no public REST API or developer documentation for the platform is published.

Source retrieved 2026-09-12

Cresta states it provides SDKs and APIs for its conversation services, but the reference documentation is gated behind login or a demo request, so endpoints, limits and terms cannot be checked publicly.

Source retrieved 2026-09-13

Every deployed crew exposes REST kickoff and status endpoints behind a bearer token, and a separate platform-wide v1 API manages automations, users and teams though it is still beta.

Source retrieved 2026-09-13

Cloud Agents API is beta on all plans and the TypeScript/Python SDKs are for all users; Admin, Analytics, AI Code Tracking and Bugbot APIs are Enterprise-only, and the India-only Start plan excludes the SDK.

Source retrieved 2026-09-02

Agent logic and tools are Git-backed and written in Python and the platform deploys headlessly, but the API reference sits behind a login so the public surface cannot be checked.

Source retrieved 2026-09-14

The product is the API: one WebSocket at /v1/agent/converse, with official SDKs for JavaScript, .NET, Python, Go and Java, all marked GA.

Source retrieved 2026-09-02

REST API creates and drives sessions under an organization scope, with a separate enterprise scope for analytics and audit logs.

Source retrieved 2026-09-02

The Devin REST API (service users, RBAC, sessions, playbooks, audit logs) is crossed out for Free and ticked from Pro upward in the plan comparison.

Source retrieved 2026-09-03

Every published app and every knowledge base is a REST API called with a Bearer key; Sandbox is capped at 5,000 calls/month, paid plans are uncapped.

Source retrieved 2026-09-02

Business plans get the Conversation API only; the Data Source API is added on Enterprise, and both sit on top of a documented REST platform with a JavaScript SDK.

Source retrieved 2026-10-01

Agents are created, driven and monitored over REST and a WebSocket protocol, with first-party SDKs for web, Python, iOS, Android and React Native.

Source retrieved 2026-09-02

A documented REST API covering search, reports and systematic review exists, but it starts at Pro; the docs list Basic and Plus as having no access at all to search requests.

Source retrieved 2026-09-14

A versioned REST API with scoped keys, idempotency and typed errors is fully documented, but the plan comparison grants API access only on Ultra and Agency, not on the three cheaper tiers.

Source retrieved 2026-10-03

Public REST API at api.factory.ai with bearer keys covers sessions, computers, org, service accounts, CI automations and wiki; TypeScript and Python SDKs exist.

Source retrieved 2026-09-02

A documented Fin Agent API drives Fin from your own stack over webhooks or SSE, but access is granted through a request form and the orchestration endpoints are published only on the Preview API version.

Source retrieved 2026-09-18

The API is the product: documented v2 REST endpoints with SDKs in Python, Node, Go, Java, Ruby, Rust, .NET, PHP and Elixir.

Source retrieved 2026-09-24

A public REST API covering chat, files, playbooks, projects and skills is open to any organisation once an admin enables it, with no extra seat, though usage draws pooled credits rather than being bundled into the subscription.

Source retrieved 2026-09-14

Team members can create API keys that admins see and revoke, but Genspark publishes no API reference, and API access to its own model is arranged by emailing a partner address.

Source retrieved 2026-09-15

Three routes: non-interactive CLI prompts on every plan, a Copilot SDK for embedding the agent, and an agent tasks REST API in public preview for starting cloud sessions.

Source retrieved 2026-09-02

Search, Chat, Agents, Indexing and Tools APIs plus a Web SDK; Search API is in the seat fee, Chat and Agents APIs draw metered usage.

Source retrieved 2026-09-02

A built-in server exposes your agents over REST for programmatic calls, and the same launcher serves the API alongside the web UI in the compiled languages.

Source retrieved 2026-09-15

Two documented programmatic paths exist: the ACP agent over stdio, HTTP or WebSocket with secret-key auth, and a goose-sdk provider library for Rust, Python and Kotlin that is still alpha.

Source retrieved 2026-09-16

Your own stack drives it through the self-hosted FastAPI REST endpoints, an OpenAPI 3.1 spec, SSE streaming and signed outbound webhooks.

Source retrieved 2026-09-16

A documented REST API with Python and JavaScript SDKs creates agents, starts sessions and triggers automations, and is listed for both plans.

Source retrieved 2026-09-30

A documented public REST API covers 13 resource groups and 78 operations, including agents, calls, campaigns, CRM, voices, and chat, with bearer-key auth. Buying numbers and paying, though, stay dashboard-only.

Source retrieved 2026-09-10

Outbound webhooks with HMAC verification are documented for alert routing, but no public Guard REST API is published.

Source retrieved 2026-09-29

A documented public REST API covers asking, summarising, tagging, sentiment, ingestion and search, with an OpenAPI spec; keys are issued by an IrisAgent contact rather than self-serve.

Source retrieved 2026-09-24

A public REST API needs no credentials, but it is read-only over the job inventory: you cannot drive the agent, apply, connect an inbox or send outreach from your own stack.

Source retrieved 2026-09-14

You drive it from your own stack through the headless CLI with an API-key token, plus an ACP mode and a GitHub Action; there is no REST API for the agent itself.

Source retrieved 2026-09-18

There is a documented public REST API with bearer keys, ticket endpoints, cursor pagination and a ticket.created webhook, plus a public OpenAPI 3.1 spec — but key creation is only offered from the Pro plan upwards, so Solo customers cannot drive it from their own stack.

Source retrieved 2026-09-26

Cloud Agent sessions can be launched by HTTP webhook and usage data has documented OpenAPI endpoints; no public API for driving the agent itself is documented.

Source retrieved 2026-09-02

The LangSmith REST API is open to every plan and Fleet agents can be triggered by API, but the Agent Server's assistants and state endpoints arrive with the Plus plan.

Source retrieved 2026-09-18

A documented REST API with /v1 and /v2 endpoints creates, edits and runs flows, and an OpenAPI spec is served from the running instance at /docs.

Source retrieved 2026-09-25

The Agent Server is an API: runs, threads, assistants, state and cron endpoints, available locally from the CLI at no cost. On the managed platform the Assistants API and the 30-plus endpoint set are Plus and Enterprise rows.

Source retrieved 2026-09-02

Programmatic access exists but only as the MCP server, authenticated by OAuth 2.1 or a Bearer MCP API key; no public REST API or endpoint reference is documented anywhere on the site.

Source retrieved 2026-09-18

An API is listed as a platform feature and CRM integrations are said to run over APIs, but no developer documentation, endpoint reference or authentication guide is published anywhere on the site or a docs subdomain.

Source retrieved 2026-09-09

Cloud agents are drivable via the Letta REST API with an API key; the recommended path is the TypeScript Agent SDK.

Source retrieved 2026-09-02

Server APIs for rooms, participants, tracks, SIP and Egress, driven from your backend with signed tokens, at 1,000 requests per minute per project. Metrics export APIs are Scale and above.

Source retrieved 2026-09-02

One API key drives every product from Python, TypeScript, Go, Java or REST.

Source retrieved 2026-09-02

A REST API is checked on every voice plan including the $249 entry tier, with webhooks appearing at Growth and GraphQL plus private endpoints reserved for Enterprise.

Source retrieved 2026-09-09

A documented REST API with API keys or OAuth2 creates and polls tasks, uploads files, manages projects, skills, agents and webhooks; per-user rate limits apply and v1 is deprecated.

Source retrieved 2026-09-19

Every registered agent and workflow is exposed as an HTTP endpoint, with OpenAPI/Swagger, a typed client SDK and OpenAI-compatible Responses routes.

Source retrieved 2026-09-02

Maven publishes SDKs and platform APIs, and Maven Apps are written in TypeScript against a named SDK package with a real deploy pipeline, so a customer team can drive and extend the platform from its own stack.

Source retrieved 2026-09-25

The product is itself a code library, and its hosting packages additionally expose an agent over OpenAI-compatible Responses and Chat Completions endpoints from your own server.

Source retrieved 2026-09-19

A documented Bearer-authenticated REST endpoint runs any published agent with variables and returns structured output, and the plan matrix ticks API calls on both paid columns.

Source retrieved 2026-09-20

A documented REST API returns conversations and contacts and can send Telegram messages, but the plan table and pricing notes place webhooks and API access on the quote-only Expert tier.

Source retrieved 2026-10-03

Documented REST APIs cover events, conversations and analytics data, authenticated with bearer tokens against a per-data-centre base URL.

Source retrieved 2026-09-20

Beyond the CLI, a versioned session protocol plus a published TypeScript SDK lets your own program drive a Muse Code session; the underlying model is separately callable over the Model API.

Source retrieved 2026-09-20

Public REST API with scoped API keys on every paid plan and self-hosted, ticked for Starter, Pro and Enterprise in the comparison table; it is switched off during the free trial and can be disabled by an operator.

Source retrieved 2026-09-02

The vendor publishes an API alongside the MCP server, with rate-limited tokens whose scopes include actions that really submit applications.

Source retrieved 2026-09-29

A documented REST API with a Bearer key covers agents, calls, campaigns, numbers and analytics, with Python, TypeScript and browser SDKs and a downloadable OpenAPI spec.

Source retrieved 2026-09-09

The product is itself a programmatic interface: agents, tools and the runner are ordinary Python objects you compose inside your own application, with no separate API tier or key to obtain.

Source retrieved 2026-09-20

The product is the API: your client opens a session on /v1/realtime and drives it with client events over WebRTC, WebSocket or SIP.

Source retrieved 2026-09-02

The Gateway can expose OpenAI-compatible chat completions, models and embeddings endpoints plus a separate responses API, but the surface ships off and you must enable it in config.

Source retrieved 2026-09-21

A headless HTTP server exposes sessions, messages and tools behind an OpenAPI 3.1 spec used to generate its own SDK.

Source retrieved 2026-09-21

A documented REST API starts and polls conversations with a bearer key, and the pricing table ticks Cloud APIs on all three plans.

Source retrieved 2026-09-21

A separate API Platform exposes Agent, Search, Router and Embeddings APIs with Python and TypeScript SDKs, billed on prepaid credits rather than a consumer plan.

Source retrieved 2026-09-02

A REST endpoint per agent exists on every paid plan, but on entry-level Gold each call is billed at a penny on top of the plan, and it is only included from Pro upward.

Source retrieved 2026-09-09

Three REST families (Agents, runtime/Conversations, Webhooks) plus WebSocket messaging and a WebRTC gateway, keyed per region.

Source retrieved 2026-09-02

The product is itself a programmable library: you construct an Agent in your own code, call run(), and can expose it as an ASGI app or UI event stream inside your stack.

Source retrieved 2026-09-21

A documented v2 REST API exists with public reference docs, but the pricing page places enterprise-grade APIs in the Enterprise tier's 'everything in Premier, plus' list, so the entry tier does not include it.

Source retrieved 2026-09-22

A documented SDK with sk- project API keys for server code plus scoped embed keys for browsers, and agents can additionally be triggered by direct HTTP requests.

Source retrieved 2026-09-22

The published REST API is an Enterprise-only admin beta for usage and membership data; it does not drive Agent builds.

Source retrieved 2026-09-22

A documented REST API with Node.js and Python SDKs covers agents, calls, phone numbers and chats, and it is listed as included on the entry pay-as-you-go plan.

Source retrieved 2026-09-23

Inbound webhooks let your own systems start an agent with a JSON POST - 10 webhooks on Individual and Teams, unlimited on Enterprise - but no public REST API reference exists; /platform lists 'MCP / API' as an interface.

Source retrieved 2026-09-03

The REST Agent API needs Agentforce enabled with an activated agent, is not supported for the 'Agentforce (Default)' agent type, and its usage draws down credits.

Source retrieved 2026-09-03

Programmatic access exists, but only as the OAuth-protected MCP endpoint; no separate REST or GraphQL API is documented on the site.

Source retrieved 2026-09-25

A REST API with a per-website key is a first-class integration, documented with an npm client library and a Next.js example, though the key requires at least one paid article credit.

Source retrieved 2026-09-25

Reads and insight calls work on the free plan, but any REST call that stages a change requires the top Infrastructure tier, so programmatic acting is gated to the most expensive plan.

Source retrieved 2026-10-03

A headless API is one of the published deployment surfaces; the reference is behind the docs sign-in, so endpoints, auth and limits are not public.

Deployed workflows expose a REST execute endpoint with sync, streaming and async modes; TypeScript and Python SDKs exist.

Source retrieved 2026-09-03

The product is nothing but an API: plain JSON events over HTTP webhooks or WebSocket, plus a REST endpoint to place outbound calls, usable from any language.

Source retrieved 2026-09-26

API access is listed as a Growth-tier addition, so the cheapest Starter plan cannot drive the product programmatically; webhooks arrive at the same tier.

Source retrieved 2026-09-26

You can drive an agent from your own stack through a generated webhook endpoint with HMAC-SHA256 signing, but no general public API is documented and the terms forbid programmatic extraction of output.

Source retrieved 2026-09-15

Any published flow can be called as a REST endpoint with an org token, but the plan comparison marks API Access as an Enterprise row while ticking the REST API plugin on Free.

Source retrieved 2026-09-09

Platform API with bearer-key auth covers agents, calls, campaigns, knowledge bases and subaccounts.

Source retrieved 2026-09-03

Delivered builds are wired to the client's stack through webhooks and HTTP endpoints per project, but TecAdRise publishes no customer-facing platform API for driving its agents.

Source retrieved 2026-09-12

A Voice Agent API exists and carries an uptime commitment, and webhooks, custom REST integration and Enterprise metrics-export APIs are advertised, but the site publishes no endpoint reference, no docs route and no key-issuing flow.

Source retrieved 2026-09-16

The whole assistant lifecycle is a public REST API under api.telnyx.com/v2: create, update, version, test and place outbound AI calls, with official SDKs in seven languages.

Source retrieved 2026-09-09

Four REST APIs (Agent, Search, Fetch, Browser) with Python and TypeScript SDKs and webhooks.

Source retrieved 2026-09-03

An OpenAPI 3.0 Orchestrator API plus OAuth external applications let your own stack drive the platform, and API triggers start an agent job over HTTP; the feature table marks API triggers for agents unavailable on Public Sector and Dedicated.

Source retrieved 2026-09-03

An Undermind API with programmatic queries and batch processing is offered to organisations via sales; no public API documentation or self-serve key is published.

Source retrieved 2026-09-26

Data, Sequences, Tasks and Analytics APIs plus Python and TypeScript SDKs are documented, but the plan table restricts open API and webhooks to Business.

Source retrieved 2026-09-27

REST API covers every capability; server and client SDKs wrap it.

Source retrieved 2026-09-03

The public release exposes Messages and Chat Completions endpoints reachable with a provisioned API key, but the docs site publishes only a placeholder OpenAPI sample instead of a real reference.

Source retrieved 2026-09-27

A versioned REST API and SSE stream exist with JWT auth, but the vendor states the HTTP API is gated behind the gateway on Vellum Cloud, so raw API work needs a local install.

Source retrieved 2026-09-27

No public REST API is documented; programmatic reach is signed outbound event webhooks from Vera Plus upward, plus a read-only connector, so you can receive events but not drive the product from your stack.

Source retrieved 2026-09-22

REST API with x-api-key auth covering agents, outbound calls, transcripts and recordings; the cheapest paid plan lists read/write API, and the Trial tier already has an API rate limit.

Source retrieved 2026-09-03

Programmatic output exists only as outbound webhooks and only on the top tier; no public REST API, keys or developer documentation are published, so you can receive events but not drive the assistant from your own stack.

Source retrieved 2026-10-03

REST API with per-organization bearer keys exposes the same tools as MCP, on free and paid accounts alike.

Source retrieved 2026-09-03

A REST API with a published OpenAPI spec creates and inspects cloud agent runs, with official Python and TypeScript SDKs; a separate read-only analytics API is Enterprise-only.

Source retrieved 2026-09-03

A documented public REST API with bearer keys covers research, extraction, pipelines, files, publications and account credits, and it is presented as the default way to drive the product.

Source retrieved 2026-09-27

A documented REST API over HTTPS with an OpenAPI 3.1 contract covering 130 operations, nine language SDKs and a Postman collection, on every paid path.

Source retrieved 2026-10-03

No public REST API for the product is documented; programmatic use is limited to the zed CLI from scripts and to extensions and ACP agent integrations built against Zed.

Source retrieved 2026-09-29

Org API keys authenticate CI integrations and the VPS install, but the only REST endpoint documented is organisation usage analytics, gated to Pro Plus and an Owner or Manager role.

Source retrieved 2026-09-09

API access is a checkmark on every self-serve plan in the comparison table; extra API volume is a paid add-on on Suite Professional.

Source retrieved 2026-09-03

A long-lived RPC child process exchanges newline-delimited JSON over stdin and stdout, and the vendor publishes a TypeScript SDK that wraps it for Node server runtimes.

Source retrieved 2026-09-28