Questions
and plain answers

One REST API and MCP server for prospecting: funding rounds that tell you why a company is worth contacting now, cited research briefs on an account, live LinkedIn reads and actions on your own connected account, and email verification before you send. One key and one prepaid balance cover every product.

Sales and growth teams, the developers who build their tools, and the AI agents that prospect for them. Anything that can send an HTTP request, or any MCP client, can call it.

Create an account, copy the key shown once in the dashboard, and send it as Authorization: Bearer on any /v1 request. The quickstart walks through checking the balance, searching funding rounds and creating a watchlist. An account can hold up to 25 keys.

No. Every new account starts with a one-time free $1 balance and no card, which buys about 111 funding records, 333 email checks or 6 research briefs at today's prices.

Per result, from prepaid credits, with no subscription and no seat count. A funding record costs $0.009 and a delivered watchlist record $0.009; an email check costs $0.003 for a valid or invalid result; a completed research brief costs $0.15. The pricing page lists every product, read from our live price list.

Credits are prepaid and 1:1 with US dollars. Buy them by card in the dashboard, any amount from $10 to $10,000, with bonus credit on larger top-ups. The balance updates once the payment is confirmed, and credits never expire.

No. A funding search that matches nothing is free, a lookup that answers 404 is free, catch-all and unknown email results are free, and any failed request refunds its whole hold.

A call you cannot pay for answers HTTP 402 with a top_up_url in the body, so an agent with no browser still knows where to send you. Nothing is charged for that call.

Every card checkout creates an invoice, and you can add a tax ID during checkout.

Rounds are complete from 2026-10-01 and partial from 2026-09-22 to 2026-09-30; only a few earlier rounds are held. An empty answer carries a coverage object that says so, so your code can tell no round from no data.

Public sources: news sites that publish every round they cover, press release wires and SEC Form D filings. Every record carries the URL of the announcement it was read from, and a search takes 9 filters, such as round, amount, investor, domain and country.

From the company's own pages, news coverage, our funding table and linked public profiles, read when you ask. A brief has 10 sections, and a field no source supports is left empty instead of guessed.

No. A people read fetches the public profile or post when you call, and anyone who asks to be removed is left out of every read that returns a person.

Four ways: pull it with the REST API, let an agent call it through the MCP server, have new funding rounds pushed to your webhook by a watchlist, or download results as CSV. The integrations page shows each one with its setup.

Any MCP client. Run prospectapis-mcp locally with npx in Claude Code, Claude Desktop or Cursor, or add the hosted server to clients that support remote MCP servers, such as Claude.ai and ChatGPT, and sign in with OAuth instead of pasting a key.

Yes, through their HTTP or webhook steps: send the request with your key in the Authorization header and map the JSON fields to the next step. A watchlist can also post new rounds straight into a webhook trigger.

Yes, 60 requests a minute per API key by default. A request over the limit gets HTTP 429 with Retry-After, and it is never billed.

One identifier: domain, website_url, company_name, company_linkedin_url, email, linkedin_url, person_name + company_name. Add optional context about what you sell and a purpose (account research, pre-call or outreach) to get a fit section with angles and hooks.

20 to 90 seconds. You submit, receive an id at once and poll it for free. It costs $0.15, held at submit, charged on completion and refunded in full if it fails.

As a one-way hash plus a short prefix, so we cannot show a key again after it is created. You can revoke a key from the dashboard at any time.

Every watchlist delivery is signed with HMAC-SHA256 using the secret returned when you created the watchlist, and carries a delivery id you can use to drop duplicates.

Yes. A removal request goes on a list that every read returning a person checks, including funding records, research briefs and people reads. The privacy policy explains how to send one.