Skip to content

docs(charge): a new hosted gateway forwards only after its upstream domain verifies #25

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
enot3615 merged 1 commit into from
Oct 25, 2026
Merged

docs(charge): a new hosted gateway forwards only after its upstream domain verifies #25

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
19 changes: 16 additions & 3 deletions charge/gateway.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -45,17 +45,30 @@ AI agent ──(pays, AIFP-1)──▶ gateway.aifinpay.io/{your-slug}/... ─
</Step>

<Step title="Configure the Gateway">
Open the **Gateway** page. Choose a slug (lowercase, e.g. `acme-search`)
and enter your upstream base URL (e.g. `https://api.acme.dev`). Save.
Open **Site settings** and press **Add gateway**. Choose a slug
(lowercase, e.g. `acme-search`), enter your upstream base URL (e.g.
`https://api.acme.dev`) and leave **Enable after verification** ticked.
Press **Review changes**, then **Apply changes**.

Your paid endpoint is live immediately:
Your paid endpoint is:

```text
https://gateway.aifinpay.io/acme-search/<any-path>
```

Requests to it are challenged with `HTTP 402` until the agent pays;
paid requests are forwarded to `https://api.acme.dev/<any-path>`.

It starts forwarding once you verify the upstream's domain. Until then it
answers `403 gateway_unavailable`, not a 402. The **Domain verification**
card on **Site settings** shows the TXT record to add at your DNS provider
(`_aifp-verify.api.acme.dev`); the **DNS connection queue** on the account
**Dashboard** lists it too. Add it, then press **Check DNS now**. Leave the
record in place: it is re-checked, and the gateway stops forwarding if it
disappears.

If your **Site URL** (under **Profile & keys**) is on the same host as the
upstream, one record verifies both.
</Step>

<Step title="Lock your origin">
Expand Down
9 changes: 6 additions & 3 deletions charge/onboarding.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -18,9 +18,12 @@ no repository, no approval, no contract:
1. Create an account and a service.
2. Give it a payout address (a standard `0x…` EVM address; settlement is on
Polygon today).
3. On the **Gateway** page, pick a slug and enter your upstream URL. Your paid
endpoint is live immediately at `https://gateway.aifinpay.io/{your-slug}/…` —
that is the URL you hand to agents.
3. On **Site settings**, add a gateway: pick a slug and enter your upstream URL.
Your paid endpoint is `https://gateway.aifinpay.io/{your-slug}/…` — that is
the URL you hand to agents. It starts forwarding once the upstream's domain
is verified: add the TXT record `_aifp-verify.<upstream-host>` that
**Site settings** shows under **Domain verification**. Until then it answers
`403 gateway_unavailable`.
4. Lock your origin so agents cannot bypass the paywall. **Read
[Hosted Gateway](/charge/gateway) before you do — the rule differs for an API
and for a site with human readers, and using the API rule on a website will
Expand Down
Loading