Launch bundle

Copy once. Send many times.

This page packages the gateway into a clean, reusable launch bundle: the manifest, the machine entry, the top paid routes, and a short pitch that builders can understand in one read.

Open manifest Open machine entry View pricing Open outreach queue

Copy-paste ready Builder-facing Base-first

Copy-paste bundle

Send this exact block to a builder, agent team, or integration lead.

Short opener Manifest Demo

Launch note

We built Alumni Gateway as a machine-readable catalog for agents and builders. The top paid routes are Registry Lookup, Network Status / Verification, and Docs / Knowledge Excerpts. Payment is Base-first by default with x402 retry semantics, and the manifest carries the settlement metadata so clients can discover, quote, pay, and retry without browser friction.

Start here:
- Manifest: https://gateway.alumniinteractive.com/gateway/manifest.json
- Machine entry: https://gateway.alumniinteractive.com/gateway/machine/
- Pricing: https://gateway.alumniinteractive.com/gateway/pricing/
- Demo: https://gateway.alumniinteractive.com/gateway/demo/

If your stack needs structured discovery, trusted verification, or compact premium retrieval, this is the fastest place to start.

1. x402 protocol integrators

They already care about payment proofs, retries, and clean buyer-side purchase flows.

2. Base ecosystem app teams

They can understand the quoted settlement asset and test small priced calls quickly.

3. Agent framework maintainers

They need structured examples that can be copied into docs, SDKs, and starter kits.

4. Wallet / checkout infra teams

They can validate the quote, pay, and retry loop against real payment proof handling.

5. MCP server builders

They already build machine-facing tools and can plug the manifest into a tool catalog.

6. AI retrieval platforms

They understand paid structured retrieval and compact answers that can be cached.

7. Browser-agent automation teams

They need route discovery, payment proofs, and reliable retry semantics more than UI polish.

8. Workflow automation builders

They can use paid execution products and budget-based repeat calls immediately.

Top 3 routes to lead with

These are the routes you should keep mentioning everywhere because they are cheap, clear, and easy to retry.

Registry Lookup

Default

/gateway/api/agents/registry/lookup

Exact metadata
Cheap and frequent
Great first purchase

Network Status / Verification

Default

/gateway/api/agents/network/status

Live trust signal
Easy to meter
Simple retry loop

Docs / Knowledge Excerpts

Default

/gateway/api/agents/docs/excerpts

Compact retrieval
Cacheable output
Immediate upsell path

Where to send it

Start with teams that already build agents, tools, wallets, or payment rails. They are the fastest path to the first paid tests.

Primary builder list

x402 protocol integrators
Base ecosystem app teams
Agent framework maintainers
Wallet / checkout infra teams
MCP server builders
AI retrieval platforms
Browser-agent automation teams
Workflow automation builders

How to ask

Ask for one paid route test, not a broad platform commitment. The goal is to get the first quote, payment, and retry cycle to happen in public.