Integration

Autobound Signal API integration

Autobound is a B2B sales-intelligence database of buying signals (SEC filings, earnings calls, hiring trends, news, funding, LinkedIn, Twitter, YouTube and podcast activity, product reviews, website changes and more). Enrich a company or a contact with its signals, search for companies or contacts showing given signal types (with subtype, firmographic and in-content filters), look up one signal, browse signal types and their history, find companies and contacts surging on buyer-intent topics, run bulk intent exports, add records to signal monitoring, and read credits, costs and request logs. Searches and enrichments are billed in credits per result. The public health checks are not exposed, and AI content generation is a separate Autobound product. Authentication is a Signal API key sent in the X-API-KEY header, created in the Autobound Signal API developer portal; it is separate from the key of the Autobound Content API.

Connect Autobound Signal API How integrations work

Ask it in chat

Say what should happen.
The workflow builds itself.

When this happens, do that in Autobound Signal API.Built from the 22 Autobound Signal API tools below, on the connection you add once.

What you can do with Autobound Signal API

Each of these is one operation on one endpoint, available both as a workflow step and as a tool an AI agent can call on its own. Nothing bundles several operations into one action, so what a run did stays readable afterwards.

Most endpoints run on the free plan. A few, mainly the ones that publish on your behalf, need a paid plan.

Export, 3 operations

get_buyer_intent_export_statusGet buyer intent export statusGETReturns the status of a buyer-intent export (exp_ for contacts, cexp_ for companies): processing, ready (with a 24-hour download_url to a JSONL file) or failed (with error and refunded credits). Free.
submit_buyer_intent_company_exportSubmit buyer intent company exportPOSTQueues a bulk export of company intent rows for the given topic ids and returns an export_id (cexp_...); poll get_buyer_intent_export_status for the JSONL download_url. Credits are charged at submit per distinct topic.
submit_buyer_intent_contact_exportSubmit buyer intent contact exportPOSTQueues a bulk export of intent-scored contacts for the given topic ids and returns an export_id (exp_...); poll get_buyer_intent_export_status for the JSONL download_url. Credits are charged at submit per distinct topic.

Enrich, 2 operations

enrich_companyEnrich companyPOSTReturns the signals Autobound holds for one company, identified by domain (preferred), company_name or linkedin_url, optionally filtered by signal type, subtype and date. Billed in credits per signal returned.
enrich_contactEnrich contactPOSTReturns the signals Autobound holds for one contact, identified by contact_email or contact_linkedin_url. Contact-level coverage is currently low; use enrich_company for the employer. Billed per signal returned.

Filter, 2 operations

list_buyer_intent_filtersList buyer intent filtersGETReturns the valid values for seniority, department, revenue buckets, employee-count buckets, countries and industries accepted by the buyer-intent search tools. Free.
list_filtersList filtersGETReturns every closed-list filter (industries, seniority, department, country, revenue and size buckets) with its accepted values, match semantics and the tools that accept it. Free.

Search, 2 operations

search_companiesSearch companiesPOSTFinds distinct companies with signals matching the filters (signal types required), newest first, each with its latest signals attached. For ICP and audience building. Billed in credits per company returned.
search_contactsSearch contactsPOSTFinds distinct contacts with signals matching the filters (signal types required), newest first, each with its latest signals attached. Filter by seniority, department, job title and company traits. Billed per contact returned.

Account, 1 operation

get_accountGet accountGETReturns your Autobound account: customer id and name, rate limit, and current credit balance. Free.

Add, 1 operation

add_to_monitoring_poolAdd to monitoring poolPOSTAdds 1 to 100 records (one company or contact plus one signal_type each) to your signal monitoring pool. All-or-nothing: one invalid record rejects the batch. linkedin-post-* records need a LinkedIn URL. May charge credits.

Company, 1 operation

search_buyer_intent_companiesSearch buyer intent companiesPOSTReturns companies surging on the given buyer-intent topic ids (from list_buyer_intent_topics), ranked by composite intent score, one page at a time via next_cursor. Billed in credits per row returned; zero results are free.

Contact, 1 operation

search_buyer_intent_contactsSearch buyer intent contactsPOSTReturns enriched contacts at companies showing intent for the given topic ids (from list_buyer_intent_topics), with company firmographics, one page at a time via next_cursor. Billed in credits per contact returned.

Cost, 1 operation

get_credit_costsGet credit costsGETReturns the effective per-endpoint credit cost table of your workspace: one row per action with its cost, description and charge mode. Free.

Credit, 1 operation

get_credit_balanceGet credit balanceGETReturns the running credit balance (balance, used, granted, since) and the per-action cost table of your workspace. There is no monthly reset. Free.

History, 1 operation

get_signal_type_historyGet signal type historyGETReturns a detection-date histogram for one signal type, to check how fresh and active it is. Accepts canonical slugs and aliases (sec-8k or 8k). Free.

Log, 1 operation

get_request_logsGet request logsGETLists your API request history for the last 30 days (path, method, status, credits), to debug failed calls or audit credit use. Free.

Signal, 1 operation

get_signal_by_idGet signal by idGETReturns one signal by its signal_id (as returned by the enrich and search tools): type, subtype, name, detection date, company, contact and the signal data. Free.

Stats, 1 operation

get_signal_statsGet signal statsGETReturns aggregate signal counts per type, the total corpus size and the last detection timestamp. Free.

Timeline, 1 operation

get_buyer_intent_company_timelineGet buyer intent company timelineGETReturns the intent-score timeline of one company across all topics from the latest Market Pulse snapshot. An unknown domain returns an empty timeline. Free.

Topic, 1 operation

list_buyer_intent_topicsList buyer intent topicsGETSearches the catalog of about 38K buyer-intent topics by fuzzy text, category or subcategory, paginated. Use the returned topic ids in the buyer-intent search and export tools. Free.

Type, 1 operation

list_signal_typesList signal typesGETLists every signal type the API serves (the valid signal_types values), with per-type label, association, description and content_filterable flag, the server defaults, and the subtype vocabulary per type. Free.

Use Autobound Signal API from Claude Code, Cursor or Codex

Connect Autobound Signal API in LiveContext, create an API key in Settings, then add the LiveContext MCP server to your client. Its Autobound Signal API operations become tools the client can call, next to every other integration you connected.

Claude Code

claude mcp add --transport http livecontext https://livecontext.ai/mcp --header "X-API-Key: YOUR_API_KEY"

Codex (~/.codex/config.toml)

[mcp_servers.livecontext]
url = "https://livecontext.ai/mcp"

[mcp_servers.livecontext.http_headers]
"X-API-Key" = "YOUR_API_KEY"

Cursor, Claude Desktop and other JSON configs

{
  "mcpServers": {
    "livecontext": {
      "type": "http",
      "url": "https://livecontext.ai/mcp",
      "headers": {
        "X-API-Key": "YOUR_API_KEY"
      }
    }
  }
}

Set up the MCP server step by step

How to connect Autobound Signal API

Create your workspace
Sign up free. Nothing to install.
Connect Autobound Signal API once
Add your Autobound Signal API connection in Settings. Every tool from this integration reuses it, and secrets are encrypted at rest and visible only to you.
Describe the job in chat
The workflow builds itself in front of you and picks the endpoints it needs. Drag the steps yourself on the canvas whenever you would rather be explicit.