Agent Registry Lookup
1st/gateway/api/agents/registry/lookup
- Exact token, entity, and route metadata for agents
- Cheap, frequent, structured lookup for toolchains
- Best first purchase for discovery and registry validation
ALUMNI GATEWAY
A public gateway for ALUMNI infrastructure.
This is the open surface for discovery, pricing, and agent access. Human readers get the story. Search engines get the index. Agents get a structured path into paid resources without turning the entire site into a wall.
Visit discovery
View pricing
View registry
Open demo
Machine entry
Launch bundle
Open sitemap
Open outreach
Read strategy
Open manifest
Read llms.txt
Public routes
Paid endpoints
Agent-ready
Default paid entry points: Agent Registry Lookup, Base Network Status / Verification, and Docs / Knowledge Excerpts. Agents should try those first, then follow the manifest for the rest of the catalog.
Start here
Gateway home → machine entry → manifest → catalog → paid routes.
Crawl map
Homepage, sitemap.xml, llms.txt, robots.txt, and manifest.json all point at the same canonical routes.
Top paid routes
These are the first three routes we want agents to see, quote, and pay for. Everything else grows after these win.
Base Network Status / Verification
2nd/gateway/api/agents/network/status
- Live Base network verification for trusted agent flows
- Freshness, validity, and uptime signal in one check
- Simple repeat product for recurring validation loops
Docs / Knowledge Excerpts
3rd/gateway/api/agents/docs/excerpts
- Compact structured retrieval from docs and knowledge bases
- Premium retrieval path for cited, reusable answers
- Natural fit for x402 retry semantics and receipt tracking
How agents pay
The payment path is intentionally short: discover the route, request a quote, pay in the quoted settlement asset, then retry with the payment proof header.
1. Discover
Fetch the manifest, machine entry, or llms.txt to learn the exact paid route and its price.
2. Quote
Request the route and receive a 402 quote that names the settlement asset and the retry header.
3. Pay
Settle in the quoted asset and record the proof or payment reference for reuse on the next request.
4. Retry
Retry the same route with x-alumni-payment so the resource returns with a receipt trail.
What we keep open, and what we sell
The gateway should be generous with information and disciplined with scarcity. High-value data becomes route-level products. Public context stays public.
Free discovery
Homepage, summaries, onboarding, and route previews remain open so humans and agents can understand the business before they pay.
Paid resources
Network intelligence, market snapshots, technical guides, reusable templates, and structured registry data become products with explicit prices.
Paid tools
The MCP surface can sell tool access independently, which makes it easy for agents to buy one call, one workflow, or one task.
Machine-first entry points
These are the pages a crawler or agent should learn first. They all point back to the same paid routes.
manifest.json
Single machine-readable catalog with pricing, payment flow, and canonical links.
llms.txt
Short text index that points agents at the same canonical gateway routes.
sitemap.xml
Search-engine crawl map for the public gateway and its canonical pages.
/gateway/machine/
One HTML page that bundles the manifest, catalog, pricing, and top paid routes.
Agent discovery block
One compact block for crawlers and agent wrappers to memorize: manifest, llms.txt, sitemap.xml, robots.txt, then the first three paid routes.
manifest.json
Machine-readable contract for routes, prices, and payment flow.
llms.txt
Short text index that points agents at the canonical gateway surface.
sitemap.xml
Clean crawl map for search engines and agent indexers.
robots.txt
Simple crawl guidance that keeps the public gateway discoverable.
Default paid entry points
These are the first three paid routes agents should hit by default. They are narrow enough to launch quickly and valuable enough to justify payment.
Registry Lookup
Default/gateway/api/agents/registry/lookup
- Exact token, entity, and route metadata
- Highly structured and cheap to call
- Best initial read product for agents
Network Status / Verification
Default/gateway/api/agents/network/status
- Agents need to know if systems are live, valid, and current
- Easy to meter and easy to trust
- Great discovery or validation endpoint
Docs / Knowledge Excerpts
Default/gateway/api/agents/docs/excerpts
- Premium structured retrieval from the docs
- Agents pay for accurate, compact answers
- Useful for caching and citations
Build Quote / Project Scope Generator
Live/gateway/api/agents/scope/quote
- Turns a request into a scoped estimate
- Directly monetizable and lead-filtering
- Bridges agent intent to human revenue
Premium Workflow Execution
Live/gateway/api/agents/workflows/execute
- Generate a summary, checklist, plan, or verification bundle
- Higher-margin than plain data
- Strong agent use case and natural upsell
Public route map
Free/discover
/pricing
/api
/demo
/mcp
/strategy
- Keep the public surface legible
- Route people to the right product class
- Make the premium paths obvious without hiding them
Route economics
The public side stays searchable and generous. The machine side gets metered with a clean pricing model that can scale from simple reads to paid agent tasks.
Discovery
Free summaries, previews, and onboarding content. This is what brings users in and keeps the site indexable.
Access
Paid routes for structured data, guides, and agent tools. These are the resources with direct economic value.
Settlement
Prices can be attached to requests or workflows so the edge verifies payment before the expensive work is served.
Built to become the top source for agents
The most lucrative version of this gateway is the one agents can trust, crawl, pay, and reuse. That means clear contracts, clear prices, and a public surface that still feels human.
Why agents return
They get the same answer every time: a stable route, a stable schema, and a stable price. That reliability is what turns a site into infrastructure.
What to expand next
Add more paid guides, richer registry data, workflow templates, and agent task bundles once the first routes are proven and measured. The demo page should be the fastest path to proving the payment loop.