Referrals as a drop-in primitive

The referral API your agent gets right the first time.

One API key. Two calls. Every mutating call is idempotent, so agent retries never double-count, and every error says exactly what to fix. Stop turning referrals into a mini-project.

→No spam. One email when your API key is ready.

✓

You’re on the list.We’ll send one email the moment the private beta opens, nothing else.

signup.ts✦ agent wiring referrals
✓ referral capturedattributed to usr_8fz…referrer· no double-count
The wedge · AI-native developer experience

Built for the agent doing the wiring, not the human reading a dashboard.

Existing referral tools assume someone is reading docs. We assume an agent is writing code into your app, and has to succeed on the first try.

01

One obvious way

A tiny, predictable surface. No integration needs more than one key and two calls. Your agent never has to pick between three ways to capture a signup.

02

Safe to retry

Every mutating call takes an idempotencyKey. When an agent retries a request, the referral is counted exactly once, never twice.

03

Errors that fix themselves

Every error says what went wrong and what to change, in plain language. No bare status code to go google mid-build.

04

The docs are the product

A complete OpenAPI spec, an llms.txt, copy-paste-correct quickstarts, and an MCP server. Everything an agent needs to find you and wire you up.

Scope · we own the loop up to money

Small on purpose. That’s the whole point.

We handle the referral loop end to end and stop before anything app-specific. You keep control of what a referral is worth.

What we handle

the referral loop, done right

  • Mint links & codes, one per referrer, ready to share anywhere.
  • Capture signups, bind a new account to the referrer whose code it carried.
  • Invite by email, referrer submits addresses, we send from shared infra. Zero setup.
  • Protect deliverability, syntax + MX validation and rate limits before anything sends.
  • Report attributions, who referred whom, counts per referrer, over a clean API.

What we don’t

deliberately out of scope

  • Reward payouts, money-touching and app-specific. We report the attribution; you decide what it’s worth.
  • Owning your users, no re-verification. We trust your “this user is real” signal and throttle.
  • A dashboard you live in, the API is the surface. A light reporting UI comes later, for humans who want a look.
Why not the incumbents

Same referral links. Different reader.

Rewardful · FirstPromoter · GrowSurf · Tolt

Built for a human

Dashboards, setup wizards, and docs written for someone clicking through a UI. Powerful once configured, a mini-project to get there, and easy for an agent to wire up almost-right.

designed around the marketing team

vs
simplereferral

Built for an agent

A machine-readable contract an agent can integrate and verify without a human in the loop. One key, two calls, idempotent, self-explaining errors. Working referrals on the first try.

designed around the code being written

How it goes in

From “I need referrals” to captured, in one sitting.

1Dev time

Point your agent at it

Install the MCP server or drop the llms.txt in context. Paste one API key.

2Dev time

It writes the two calls

The agent scaffolds the capture call and share UI into your app, then tests them live against real responses.

3Runtime

Your app calls the API

A real person signs up carrying a code; your backend captures it over REST. Attribution done, no double-counts.

Private beta · opening this quarter

Get an API key before everyone’s agent does.

We’re onboarding a small first cohort of builders. Leave your email and we’ll send a key when the beta opens, one message, no drip.

✓

You’re on the list.Watch for one email when the private beta opens.