Signalbase + Orthogonal integration

Orthogonal is the unified API for AI agents: one key, hundreds of APIs, pay per request. Signalbase is live on their catalog as the event layer, so the same SDK your agents already use can query funding rounds, hiring momentum, job changes, companies and people, each signal verified at the source and delivered with the company context attached.

An agent working from static data knows who a company is. Working from Signalbase through Orthogonal, it also knows what just happened there, which is the difference between a research summary and a reason to act.

What agents can do

  • Build fresh target lists from funding. Seed and Series A rounds from the last 30 days, filtered by country and round type, with investors and sources on every row.

  • Detect hiring momentum before databases catch up. Filter hiring signals by department, seniority and geography, and route accounts building a sales team straight to outbound.

  • Catch new decision makers as they land. Job change signals return the person, the move and the matched company, so the agent can explain why the timing matters.

  • Qualify accounts against your ICP. Company search runs independently of the signal feed, for list building and CRM checks before the agent spends a credit.

  • Enrich the list you already have. Post a CSV of accounts and get funding, M&A, hiring, job-change and investor intelligence back, so the agent knows which rows deserve attention now.

  • Find the person behind the event. People discovery connects operators and buyers to recent signal activity, when the workflow needs a name alongside the account.

Static company data answers who a company is. Signalbase answers what happened, when it happened, and why it matters.
Christian Pickett·Co-founder, Orthogonal

Agent-native payments

This is the part no other integration of ours has. Signalbase on Orthogonal supports x402, the protocol for native HTTP payments, so an agent can pay for an individual API call with USDC and no API key at all. It also works through MPP, the machine-payment standard co-authored by Tempo and Stripe, which accepts stablecoins, cards and Bitcoin on the same endpoint. An autonomous agent can discover the signal feed, pay for exactly the calls it needs, and act on the result inside one run.

Setup

  1. 1
    Create an Orthogonal account and grab your API key. New accounts include free credits to test with.
  2. 2
    Call Signalbase from the Orthogonal SDK with api: "signalbase" and the endpoint path, for example /signals/funding.
  3. 3
    Filter with the same parameters the Signalbase API takes: countries, round types, departments, seniorities, date presets.
  4. 4
    Or skip the key entirely and let your agent pay per call over x402 or MPP.

Signals available through Orthogonal

Fundinground type, amount, investors, announced date, company context, sources
Hiringdepartment, seniority, location filters, open roles, source
Job changesperson, previous and new role, matched company context
Companiessearch by industry, geography, headcount; full profiles
Peopletitle and geography filters, connected to recent signal activity
CSV enrichmentpost an account list, receive signal intelligence per row

The full walkthrough with runnable SDK snippets is in Orthogonal's launch post.

How teams use it

Sales

An agent drafts outreach from a round that closed this week, while the event is still a reason to write.

RevOps

CRM records refresh when an account starts hiring or a champion changes roles, without a batch job.

Recruiting

Watch for companies expanding a function, routed by department, seniority and location.

Research

Track funding trends, map active investors and keep an internal company graph current without building a sourcing system.

Orthogonal integration

The event layer for your agent stack

Query live signals through the Orthogonal SDK, or let your agents pay per call over x402 and MPP.

Tested by 700+ GTM teams · 500 trial credits included

Orthogonal integration FAQ

No. Your Orthogonal key covers Signalbase along with the rest of their API catalog, and usage is billed per request through Orthogonal. A direct Signalbase plan makes sense when you want webhooks, the MCP server, CSV tooling in the dashboard, or volume pricing.