Integration guides

Release boundary

Pro Rout is Solana only: Human-owned Agent identity, regular SPL tokens and one Agent NFT collection. NFT ownership and token swapping are still being built. No schema, link or model output establishes a swap or a Solana wallet signature. The web app's Trade, Portfolio and Community screens show labelled sample data.

Current authentication is invitation-led, email-only. Use /release.json and the release ledger for the deployed source; documentation dates are not deployment identifiers.

Links carry choices, not authority

A link into Pro Rout may carry a finite presentation choice, such as a selected Agent name. It never carries tokens, identity, balances, ownership or an arbitrary return address.

Private application API

Ordinary private profile and draft operations are supported. The existing workspace boundary keeps these operations when its account rollout is enabled:

Operation	Boundary
GET /api/account/workspace	Read existing saved records; verified identity and invitation required
PUT /api/account/workspace	Existing preference; expected revision and account approval required
Saved workspace download	Account-owned export of existing records
PUT /api/account/creator-draft	Paused: 503 WORKSPACE_DISABLED; existing records stay preserved

These are private application operations, not partner API scopes or a browser token to copy into an agent. The local MCP adapter never calls them. Authentication, invitation, origin and ownership checks are enforced on the server; account changes and sign-out clear private views.

Builder access

Hosted builder access is approved manually through @irrational_cto and uses separate, scoped, expiring credentials. Keep them on your server — never in URLs, browser code, screenshots or a public repository. A DM, sign-in or payment does not activate an integration. Private account writes and vault management are not granted.

Later management API

Future account or vault management needs object-level ownership checks, auditable delegated approval and separately reviewed signing policies. None of these permissions can be inferred from holding an NFT image or paying a fee.

Local x402 sandbox

Preview only: this loopback exercise is for approved source users. It is not billing, swapping or production execution.

The sandbox runs a configuration-report exercise locally. It uses x402 v2 HTTP headers with an explicit custom mock scheme and never accepts real payments.

corepack pnpm install --frozen-lockfile --ignore-scripts
corepack pnpm --filter @pro-route/report-sandbox... build
corepack pnpm --filter @pro-route/report-sandbox test:run
corepack pnpm --filter @pro-route/report-sandbox demo

The demo starts a temporary loopback server, receives a 402 challenge, explicitly approves a mock payment and gets a deterministic report. It also rehearses pending and interrupted responses and checks that each operation is charged once. Browser origins and remote hosts are rejected; never publish the harness through a tunnel.

• Missing permission and invalid input fail before a payment challenge.
• Same-operation retries return the same report and mock receipt.
• Decline, pending, expiry and a lost response have explicit recovery paths.
• The mock network is prdemo:local, the asset is DEMO-CREDIT and receipts start with mock:. They are not transaction hashes.

Restarting clears every operation and restores the 100-credit sample budget. Live settlement still needs a reviewed Solana asset, recipient and price, durable storage and reconciliation. A payment never grants ownership or management rights. See the wire reference and retry guidance.