Autobound
Also known as: Autobound Signal API, Autobound CoPilot, Autobound AI Studio
B2B signal intelligence sold as infrastructure, with 700+ signal types from 35+ sources reachable by REST API, MCP server or bulk file, and an AI Studio layer that turns those signals into personalized outreach pushed to Outreach and Salesloft.
Autobound sells B2B signal intelligence, a database of more than 700 signal types drawn from over 35 sources across 250 million contacts and 50 million companies, covering SEC filing analysis, hiring surges, tech stack changes, competitor activity, news and social. Customers reach it through a REST API with published pricing per endpoint, a hosted MCP server that works with Claude, Cursor and other MCP clients, OpenAI function calling, a Claude Code integration, GCS push, or flat file bulk licensing into their own infrastructure, and other platforms license the same data white label to embed in their products.
Autobound publishes its coverage instead of just asserting it, with audited volumes and fill rates per signal type, measured freshness and geography, backward compatible schema versioning on 90 day migration windows, and weekly quality reports for enterprise partners. On top of the data sits the outreach product the company started with.
AI Studio generates personalized emails, LinkedIn messages and call scripts from those signals, assembles sequences, and pushes them into Outreach or Salesloft or sends directly, with built in moderation, role based approval routing to marketing and legal, configurable insight controls over which signals may be used, and auditable trails over what went out. Autobound holds SOC 2 Type II with annual third party audits, and its security covers SSO via SAML and OIDC, granular role based access control, exportable audit logs, configurable retention, and dedicated infrastructure or private service endpoints for enterprise customers. Pricing is usage based credits, from 1,000 free on signup and a $19 starter pack up to enterprise packs, with credits that never expire.
Vendor details
Canonical URL
https://autobound.ai
Category
GTM / revenue agent
Subcategory
Sales — intent-based outreach
Funding status
Private. States 2,500-plus companies as customers and names TechTarget as an OEM partner embedding its signal data, alongside AiSDR and Skuid as customers. Carries G2 category badges for 2025 and 2026.
Company status
independent
Use cases & customers
Primary use cases
Target customers
Deployment options
Integrations
Autobound pushes generated content into Outreach and Salesloft or sends directly, syncs with Salesforce and HubSpot, works through Gmail and Outlook, and carries a Chrome extension for LinkedIn surfaces. It draws inbound data from more than 35 external data sources covering SEC filings, hiring, tech stack, news, social and competitor activity. The signal layer is delivered outward by REST API, a hosted MCP server for Claude, Cursor and any MCP client, OpenAI function calling, Claude Code, GCS push, or flat file bulk licensing into the customer's own infrastructure, and is licensed white label to other platforms under an OEM route with TechTarget as an embedding partner.
In practice
You're paying three or four vendors for enrichment, intent and firmographics. Autobound consolidates them into one API with published coverage and fill rates per signal type, so you can check completeness before you build on it.
You want signal data inside your own assistant or product. Autobound ships an MCP server for Claude and Cursor, OpenAI function calling, GCS push, and a white-label OEM route for embedding the data in what you sell.
Your reps write generic emails because researching each prospect takes too long. AI Studio turns the signals into personalized emails, LinkedIn messages and call scripts, with moderation and approval routing before anything is pushed to Outreach or Salesloft.
Sources & related URLs
Related / legacy domains
Agentic Index coverage score
8.0 / 14 capabilities · 57%
| Integrations & Tool Calling | Full |
|---|---|
|
Integrations run in both directions. Into the customer's stack, Autobound connects to CRM through Salesforce and HubSpot and to sequencers through Outreach and Salesloft, where AI Studio pushes content or sends directly. It works through Gmail and Outlook mailboxes and reaches LinkedIn through a Chrome extension. Coming in, more than 35 external data sources feed the signal layer, spanning SEC filings, hiring data, tech stack detection, news, social and competitor activity. An OEM and embed route licenses signal data into other vendors' products, with TechTarget as an embedding partner. Flat file delivery pushes bulk data into the customer's own infrastructure on a weekly refresh. The MCP server, Claude Code and OpenAI function calling point the other way and let outside assistants call Autobound. Sourceautobound.ai/integrations and autobound.ai/for-platformsread 2026-09-02 |
|
| Workflow Orchestration | Partial |
|
Signals are gathered from more than 35 sources, and content is generated for email, LinkedIn and call scripts. Sequences are assembled in AI Studio, and the result is pushed into Outreach or Salesloft or sent directly. Moderation and approval routing sit inside the same flow. Autobound is a signal and content layer that runs inside other engagement platforms and does not execute work on its own. On LinkedIn it does not send on the user's behalf. The company now leads with signal infrastructure sold by API, not an agent that runs a sales motion end to end. Sourceautobound.ai/platform/ai-studio and autobound.ai/use-case/brand-safety-and-scaling; autobound.ai/integrationsread 2026-09-02 |
|
| Knowledge Grounding & RAG | Partial |
|
The signal corpus holds more than 700 signal types from more than 35 sources, across 250 million contacts and 50 million companies. Signals include SEC filing analysis, hiring surges, tech stack changes, competitor activity, news and social, with measured coverage and fill rates per signal type and a weekly refresh. The corpus is Autobound's own product, assembled about the prospect and delivered per request, and it is what the customer pays for. The customer's own material reaches it only as CRM activity, read as one signal source among the 35. Autobound does not ingest the customer's positioning, collateral, case studies or product documentation into an indexed layer the agents read. Sourceautobound.ai/signal-data and autobound.ai/use-case/brand-safety-and-scalingread 2026-09-02 |
|
| Human Oversight & Guardrails | Full |
|
Governance is Autobound's stated differentiator. It argues against AI tools that operate as uncontrollable black boxes and says its platform is built with enterprise governance at its core. It ships built in moderation, role based approval flows and configurable insight controls that give granular command over every message. Brand guidelines are enforced centrally, so messaging cannot go off brand or make unapproved claims. Approval flows route content to legal and marketing instead of leaving review to the sender, and they run in Autobound's own product, not in a downstream tool. On LinkedIn a person reviews and sends, so nothing goes out without one. Insight controls limit which signals may be used, and auditable trails record what happened. Sourceautobound.ai/use-case/brand-safety-and-scalingread 2026-09-02 |
|
| Security, Identity & Governance | Full |
|
SOC 2 Type II covers availability, confidentiality and privacy, with annual audits by independent third parties and reports available under NDA. Autobound is GDPR compliant, with DPAs for enterprise customers, and supports CCPA with opt out and deletion workflows. Third party penetration testing runs every year with remediation tracking, and customers may run their own assessments. SSO works via SAML 2.0 and OpenID Connect, with Okta, Azure AD and Google Workspace. Granular role based access control comes with predefined Admin, Developer and Read-Only roles, plus custom roles on enterprise plans. Scoped API keys carry configurable permissions and rotate with zero downtime. Data retention is configurable, with full deletion on account closure, and IP allowlisting is available. Data is protected by TLS 1.3 with HSTS preloading and optional certificate pinning, and by AES-256-GCM at rest with Google Cloud KMS and automatic key rotation. Operations add 24/7 monitoring with anomaly detection, SAST and DAST in the pipeline, critical patches within 24 hours, and an incident response plan with a one hour acknowledgment SLA. Audit logging is included. Sourceautobound.ai/securityread 2026-09-02 |
|
| Observability & Auditability | Full |
|
Comprehensive audit logs cover all API access, configuration changes and user actions, and customers can export them for compliance reviews. Every signal delivered has a full audit trail, so the inputs behind a generated message can be traced to the signals that produced it. Messaging workflows are auditable too. Continuous monitoring with anomaly detection on access patterns runs across the same infrastructure. Sourceautobound.ai/security and autobound.ai/use-case/brand-safety-and-scalingread 2026-09-02 |
|
| Memory & State Persistence | Not documented |
|
CRM activity is read as one of the signal sources, so prior interaction history informs what is generated. Campaign state persists in campaign tables, and the signal layer carries temporal depth. Retention of signal data is configurable under plan terms. No agent writes anything that an agent later reads back. There is no memory object, no state per agent across runs and no control over what the system has learned. Sourceautobound.ai/signal-data, autobound.ai/platform/ai-studio and autobound.ai/securityread 2026-10-01 |
|
| Deployment & Data Residency | Partial |
|
Tenant data is logically isolated at the database level, and enterprise customers can ask for dedicated infrastructure. VPC isolation, private service endpoints and IP allowlisting are available to enterprise customers, and there are no public database endpoints. The custom volume tier includes dedicated infrastructure alongside SSO and an SLA. Flat file delivery ships bulk data into the customer's own infrastructure on a weekly refresh. Hosting is on Google Cloud with multi region redundancy, which Autobound runs for its own availability. Customers cannot choose a region, and there is no EU option or residency commitment. Sourceautobound.ai/security and autobound.ai/pricingread 2026-09-02 |
|
| Prebuilt Agents, Templates & Packs | Partial |
|
What ships is a set of configurable modules, not named agents. They include an insights engine, AI Studio as the multichannel command center where generated content becomes campaigns, a custom researcher, campaign tables, and message templates aware of persona and sales stage. There is no library of named agents or job shaped templates to browse and select from, and the message templates are the only templates. Customers can browse a signal catalog of more than 700 signal types. Sourceautobound.ai/platform/ai-studio and autobound.ai/signal-data; autobound.ai/integrationsread 2026-09-02 |
|
| Triggers & Channel Coverage | Partial |
|
A person starts the outreach, and signals feed it continuously. Outreach covers email, LinkedIn messages and InMails, and call scripts, with sequences assembled in AI Studio and pushed to Outreach or Salesloft or sent directly. The signal layer refreshes continuously, with measured freshness per signal type, so what there is to say changes as the world changes. Signals shape what is said but do not start anything. No event trigger, signal threshold or subscription starts outreach without a person. The REST API offers a subscribe route and GCS push for signal delivery, but these push data to a subscriber and do not set an agent to work. Sourceautobound.ai/signal-data, autobound.ai/signal-api and autobound.ai/platform/ai-studioread 2026-09-02 |
|
| Model Flexibility & Routing | Not documented |
|
The underlying model and provider are not named. Customers get no model selector, model choice per agent, routing policy, or option to bring their own model or their own key. The MCP server, Claude Code and OpenAI function calling let a customer drive Autobound from an assistant of their choosing, but not choose the model inside it. Sourceautobound.ai/security and autobound.ai/signal-dataread 2026-09-02 |
|
| APIs, SDKs & MCP Extensibility | Full |
|
The developer platform is how the company sells. A developer hub offers a quickstart, and API endpoints cover enrich, search, intent and email verification, with an API reference at autobound-api.readme.io. The REST API supports search, enrich and subscribe, with scoped API keys and configurable permissions. For agents there is an MCP server for Claude, Cursor and any MCP client, a Claude Code integration, OpenAI function calling with signals, and a For AI Agents page covering MCP, tool calls and GCS push. An OEM and embed route licenses white label signal data into other vendors' products, and flat file delivery ships bulk data to the customer's own infrastructure. Pricing is set per endpoint, and the API is self serve from a free credit allocation. Sourceautobound.ai/developers, autobound.ai/apis and autobound.ai/integrations/mcpread 2026-09-02 |
|
| Testing, Debugging & Optimization | Partial |
|
A public coverage report gives audited volumes and fill rates per signal type, with measured geography, join keys and freshness, so customers can check how complete a signal is before building on it. Every signal passes automated quality checks with anomaly detection on volume, coverage and extraction accuracy. Enterprise partners receive weekly quality reports. Schema versions stay backward compatible with 90 day migration windows, so a change can be tested before it lands. None of this tests the generated content itself. There is no sandbox, replay, scored evaluation or dry run before content reaches a prospect, and the built in moderation is a guardrail, not a test. Sourceautobound.ai/signal-coverage and autobound.ai/use-case/brand-safety-and-scalingread 2026-09-02 |
|
| Browser & Computer Use | Not documented |
|
Everything runs through programmatic routes. The signal layer is delivered by REST API, MCP, function calling, GCS push or flat file, and content is pushed into Outreach and Salesloft through integrations. The Chrome extension reads a LinkedIn profile the user is already viewing and drafts into it, and the person reviews and sends. No agent operates the browser, and there is no headless session or screen operation. Sourceautobound.ai/signal-api and autobound.ai/platform/ai-studioread 2026-09-02 |
|
The Agentic Index coverage score grades every vendor Full, Partial or Not documented against the same 14 buyer facing capabilities, from public evidence only. Each capability links to how all vendors in the index score on it. How this evidence is graded
Pricing
Free to start with 1,000 credits and no card. Paid packs are one-time: $19 for 2,000 credits, $49 for 5,444, $149 for 19,867, $499 for 83,167, $1,299 for 288,667 and $4,999 for 1,249,750.
usage credits, metered per API action
Included quota
All 35-plus signal sources, the REST API, the MCP server and buyer intent data are included on every plan, including the free allocation; the tiers differ only in credit volume and unit price. Published unit rates: search 2 credits per result, enrich 2 credits per signal returned, buyer intent 1 credit per contact, bulk export 50 credits plus 5 per topic with unlimited rows. Unit price falls from $0.0095 per credit at Starter to $0.004 at the $4,999 tier, a stated 58 percent saving.
What is public
An unusually complete self-serve rate card. Six credit packs are published with price, credit volume and unit price, from $19 for 2,000 credits at $0.0095 each to $4,999 for 1,249,750 at $0.004, alongside a stated 1,000 free credits on signup with no card. Consumption is published per endpoint, credits are stated never to expire, packs pool, and the free-endpoint list is spelled out. Enterprise packs are given a range, $10,000 to $40,000, and only custom volume above 11.5 million credits, flat-file licensing and SLA terms route to sales. Confirmed against the complete site navigation, which carries one pricing page and a contact-sales route.
Billing mechanics
Prepaid credit packs rather than a subscription. A buyer purchases a pack outright, draws it down per API action, and tops up whenever; balances pool across purchases and never expire. Metering is published per endpoint: search 2 credits per result, enrich 2 credits per signal returned, buyer intent 1 credit per contact, bulk export 50 credits plus 5 per topic with unlimited rows, and zero-result requests free. Unit price decreases with pack size across six published tiers. Flat-file bulk delivery is an alternative contract for high volume, positioned by the vendor as cheaper above roughly 50,000 enrichments a month, with weekly refresh into the customer's own infrastructure.
Cost watchouts
Cost is driven by how many signals come back, not by how many calls are made: enrich charges 2 credits per signal returned, and the vendor's own worked example puts a company enrich at roughly 8 signals, about 16 credits, so 1,000 companies is about 16,000 credits and exceeds every pack below Pro. Search charges per result rather than per query. The mitigations are real and published, though: zero-result requests are free, credits never expire, packs pool, and exports are priced by topic count rather than row count so a 10 million row pull costs the same as one row. SSO and dedicated infrastructure sit above the published tiers on custom volume.
Variable cost rationale
Spend is prepaid and capped by the pack purchased, so there is no runaway billing, but the credit-to-work ratio is easy to misjudge because enrich charges per signal returned rather than per request. The published per-endpoint rates and the vendor's own worked example make the exposure calculable in advance, which most of this lane does not offer.
Additional watchouts
Read the metering before sizing a budget: charging per signal returned rather than per call means a single company enrich can cost around 16 credits, so volume assumptions built on call counts will understate spend by roughly an order of magnitude. SSO and dedicated infrastructure are not on the published tiers and require custom volume, which matters for buyers whose security review expects SSO. The published tiers price signal data; the outreach product's commercial terms are not broken out.
Overage / add-ons
No overage in the usual sense, since packs are prepaid and drawn down. Running out means buying another pack, which pools with the existing balance. Enterprise packs run $10,000 for 2.6 million credits to $40,000 for 11.5 million; beyond that rates are quoted.
Sales call required
No, self serve available
Free / trial
1,000 free credits on signup, no credit card required. Zero-result requests are free, and browsing the catalog, topics, filters, account and export status never draws on the balance.
Lowest paid plan
Starter, $19 one-time for 2,000 credits at $0.0095 per credit.
Commercial notes
Sold to three distinct buyers: data and revenue operations teams consuming the API, platform partners licensing signal data white-label under an OEM route with TechTarget named, and sales teams using the AI Studio outreach layer. States 2,500-plus companies as customers, a 99.9 percent uptime SLA, sub-200ms API response and zero security breaches. The published positioning is B2B signal intelligence infrastructure rather than an AI SDR.
Key ambiguities
The self-serve rate card is complete and needs no interpretation. What is not published: flat-file licensing cost, custom volume rates beyond the $40,000 enterprise pack, SLA terms, and the price of the AI Studio outreach product as distinct from signal credits, which the current pricing page does not separate.
Cancellation / refund
Credit packs are one-time purchases rather than subscriptions, so there is nothing to cancel; unused credits never expire and multiple packs pool into one balance. Failed export jobs are not charged. Flat-file licensing and custom volume run on contract, terms not published.
Support SLA / resale
Team adds a dedicated CSM and enhanced analytics; Scale/Enterprise add onboarding, account management, webhooks, visitor-intent tracking, multi-CRM; Signal Data Enterprise/Flat-File customers can white-label, OEM partners embed via API with custom SLAs
Missing data
Published first party: the free allocation, all six credit pack prices and credit volumes, per-credit unit prices, the per-endpoint consumption rates, the enterprise pack range, credit expiry, pooling, and the free-endpoint list. Not published: flat-file licensing cost, custom volume rates, SLA terms and any separate price for the AI Studio outreach product.
Related vendors
- 11x — AI digital workers (Alice for outbound SDR work, Julian for inbound…
- 1up — AI answer engine for sales teams that automates RFPs and security…
- Actively AI — GTM superintelligence platform that trains a custom reasoning model…
- Aircover.ai — AI sales assistant that delivers real time in call coaching, a…
- AiSDR — AI SDR platform with multichannel outreach automation, quota visible…
- Akkari — Autonomous customer ops agent that captures every commitment,…
Alternatives to Autobound
The closest documented capability profiles to Autobound among GTM and revenue agents tracked by Agentic Index, ordered by similarity on the same 14 point evidence the rankings use. No vendor pays for placement.
- Arphie8.0 / 14Adds documented Model Flexibility & Routing
- Connecty AI9.0 / 14Fuller documented coverage on Knowledge Grounding & RAG and Prebuilt Agents, Templates & Packs
- Loopio8.0 / 14Fuller documented coverage on Workflow Orchestration and Knowledge Grounding & RAG
- Shopify Sidekick8.0 / 14Fuller documented coverage on Knowledge Grounding & RAG and Triggers & Channel Coverage
- Jasper9.5 / 14Adds documented Model Flexibility & Routing
- nRev AI9.5 / 14Fuller documented coverage on Workflow Orchestration and Prebuilt Agents, Templates & Packs
Similarity is computed from each vendor's Agentic Index coverage score evidence, axis by axis, not from the totals. How this evidence is graded