Building on it
Integration API
A small server adapter connects one fixed supplier offer to a verified Solana payment and persistent job record.
API boundary
| Route | Responsibility |
|---|---|
| GET /api/compute/config | Return public integration availability and missing requirements. |
| POST /api/compute/quote | Validate the service, input and budget; return a fixed, expiring quote. |
| GET /api/compute/jobs | Read authenticated formal history from durable server storage; currently unavailable. |
| POST /api/compute/jobs | Verify payment and create or recover one idempotent provider job. |
| GET /api/compute/jobs/:id | Return authorized provider-derived status, output and receipt. |
Current implementation status
This build provides an explicit unavailable boundary and a separate browser demo. No live provider or payment adapter was supplied. Real quote and job actions respond unavailable instead of simulating a paid execution.
Live integration checklist
| Configuration / implementation | Current status |
|---|---|
| SOLANA_CLUSTER / SOLANA_RPC_URL | Demo cluster devnet; live RPC not configured. |
| SOLANA_USDC_MINT / SOLANA_RECIPIENT | No approved payment mint or recipient configured. |
| SOLANA_TOKEN_PROGRAM_ID / SOLANA_PROGRAM_ID | Token program not configured; custom program only if used. |
| COMPUTE_PROVIDER_URL / COMPUTE_PROVIDER_API_KEY | No live supplier endpoint or credentials configured. |
| Fixed task offer | One browser demo; real model, limits, provider price and retention still required. |
| COMPUTE_JOB_STORE_URL | No durable formal job store configured. |
| Payment builder / verifier | Not implemented; no wallet signing or broadcasting. |
| Provider execution adapter | Not implemented; no external compute request. |
| Payment replay / refunds | Durable idempotency and paid-failure reconciliation required. |
Persistence boundary
GET /api/compute/jobs and GET /api/compute/jobs/:id are the formal history interface. They currently return 503 because no durable job store or provider adapter is configured. No formal record is fabricated or moved to localStorage.
A live deployment must persist job IDs, request and result references, usage, quote amounts, verified payments and lifecycle updates with access control and replay protection. Local preview fixtures are not formal settlement records.
Server responsibilities
- Keep provider credentials and RPC secrets on the server.
- Validate input, output limits, budget, quote expiry and buyer authorization.
- Verify actual token transfers before provider submission.
- Persist quotes, signatures and job IDs with idempotency and access control.
- Implement result retention, timeouts, failures and refund records.
Dashboard and agent clients
| Control | Behavior and source |
|---|---|
| Connect wallet | Request a public Solana address from an installed wallet. |
| Service and budget | Choose the fixed offer and maximum USDC spend. |
| Review quote | Request server pricing when configured; demo pricing stays labeled. |
| Extract / Inspect / Summarize | Load prepared examples through the same text service and quote flow. |
| Run demo | Record a local preset result or custom preview; no provider call or payment. |
| Replay | Read the saved Job events; update rack focus without execution. |
| Receipt Inspector | Check file structure, Job association and hashes in the browser. |
| Job ID / Result | Open task details or result preview; copy or download the output. |
| Demo history | Restore browser-local demo records after refresh; clear with confirmation. |
| Payment link | Open only an actual verified Solana transaction. |
Programs and on-chain scope
A standard USDC transfer does not imply a custom RACKVO program exists. If a chosen integration requires a program, its ID and verified interface must be configured. No replacement contract address or audit claim is invented.
Last updated 29 October 2026.