makecallable_>
claim a seat

MakeCallable

Make your API callable by AI agents

MakeCallable is like shipping your own Upwork-style MCP move — for any product with an OpenAPI. Paste the spec. Get a hosted MCP URL. Watch agent calls. Tag the revenue.

MakeCallable Console

How you use MakeCallable · connect MCP, start talking

You → Claude

Find a senior React role in Berlin that pays over €90k and apply with my profile. Use Acme Jobs.

Claude · used Acme Jobs MCP

Called search_jobs · get_job · submit_application

Applied to “Senior React Engineer — Berlin” at Northpine (€95–110k). Confirmation id app_8f2c. Want me to track status?

Your dashboard

3 tool calls logged · application closed · you tag $2,400 GSV

the shift

Agents don’t browse your marketing site. They call tools.

If growth still means “rank on Google and hope a human clicks,” you’re playing yesterday’s game. The durable channel is an agent completing the job through your API — and you being able to prove it made money.

What do people use MakeCallable for?

  1. / 01

    Marketplace & jobs APIs

    Agents search, apply, book. You see the calls — and tag the hire or purchase when it closes.

  2. / 02

    SaaS product APIs

    Expose the actions power users already take. No second “agent stack.” Same OpenAPI.

  3. / 03

    A public edge on internal tools

    Ship a capped, authenticated MCP surface. Learn which tools agents actually call before you overbuild.

OpenAPI in. MCP out. Clients you already use.

Install the hosted URL in Cursor, Claude, or any Streamable HTTP MCP client that can send a Bearer token. Full per-client steps on the agents page.

  • / 01Hosted MCP URL from OpenAPI JSON
  • / 02Bearer auth on every request
  • / 03Your upstream base URL + secret
  • / 04Call log + top tools + 7-day series
  • / 05Manual revenue / GSV tagging
  • / 06SSRF guard, rate limits, seat caps

Building MCP yourself is a quarter. Measuring agent revenue is the product.

Most teams either ignore agents, or burn weeks on SDK wiring and still can’t answer “did this traffic pay?” MakeCallable hosts the MCP surface and gives you the call log + GSV tagging so the thesis is measurable — under a hard seat cap while we stay hands-on.

FAQ

OpenAPI JSON for your API, a base URL agents should hit, and an optional upstream Bearer or API key. Sign in with a magic link, import the spec, install the MCP URL.

Anything that speaks remote Streamable HTTP MCP with a Bearer token — Cursor, Claude (Desktop / Claude.ai connectors with Request headers, or Claude Code), VS Code, Windsurf, and custom agents. ChatGPT custom MCP is OAuth or no-auth only, so it cannot use MakeCallable until an OAuth broker ships.

No. Keep the REST API you have. We map OpenAPI operations to tools, host the MCP endpoint, and proxy authenticated calls upstream.

Every proxied tool call is logged. When an agent-driven outcome closes, you tag a revenue / GSV event so you can attribute the traffic.

Early access is capped (default 50) so support stays real. When seats fill, the page takes a waitlist — no silent fail.

Auth and Postgres on Supabase in eu-central-1. Upstream calls go to the base URL you set. Private, localhost, and metadata hosts are blocked.

Email hello@makecallable.com. Include your project slug, a redacted OpenAPI snippet, base URL host, and the client you’re installing.

Start on a capped seat.

Import OpenAPI. Install MCP. Tag the first revenue event. When seats fill, the waitlist keeps your place.