Spot Check. REQUIRES ?host= on the paid request — a signed request without it is refused before the gate and no money moves. Name a host and get what this observatory already holds on it, signed: corpus rounds and verdicts as recorded, when we last actually knocked, our coverage of the window since we met it, and the gaps with their reasons. Read from the books at the counter — no request is made to the host, so the answer is as fresh as our last round and no fresher, and sa…
https://scvd.storeSpot Check. REQUIRES ?host= on the paid request — a signed request without it is refused before the gate and no money moves. Name a host and get what this observatory already holds on it, signed: corpus rounds and verdicts as recorded, when we last actually knocked, our coverage of the window since we met it, and the gaps with their reasons. Read from the books at the counter — no request is made to the host, so the answer is as fresh as our last round and no fresher, and sa…
A Small Blessing. One blessing slip from a 87-slip jar filled in 2 seasons so far, never the same slip twice in a row, delivered instantly with purchased_text: an ed25519 envelope binding the exact words and purchase certificate. Full listing: https://scvd.store/menu/small_blessing. MCP tool: buy_small_blessing.
The Confession. REQUIRES ?confession= on the paid request — a signed request without it is refused before the gate and no money moves. A signed absolution certificate and a private confession_receipt proving the exact stored text and purchase certificate. Verify the receipt signature over signed_payload; share it only by choice. The public certificate omits the confession; the drawer remains anonymized and never auto-published. Full listing: https://scvd.store/menu/the_confe…
Research Comparison. REQUIRES ?urls= on the paid request — a signed request without it is refused before the gate and no money moves. One signed comparison: live atomic payment terms, dated host history and gaps, same-endpoint network changes, shared receivers and limits. No research quality or ownership verdict. Full listing: https://scvd.store/menu/research_comparison. MCP tool: buy_research_comparison.
Batch Spot Check. REQUIRES ?hosts= on the paid request — a signed request without it is refused before the gate and no money moves. Read existing host records as a signed batch; no live probes or rankings Full listing: https://scvd.store/menu/batch_spot_check. MCP tool: buy_batch_spot_check.
The Daily Fortune. The day's fortune and fortune_date (UTC), with purchased_text: an ed25519 envelope binding the exact words, date and purchase certificate. Every buyer today reads the same line. Full listing: https://scvd.store/menu/daily_fortune. MCP tool: buy_daily_fortune.
Settlement Reconciliation. REQUIRES ?tx_hash= on the paid request — a signed request without it is refused before the gate and no money moves. A signed JSON observation of one Base transaction reconciling two numbers — the USDC that moved and an attributable fixed authorization value or declared cap — with cap_source and cap_observed naming where the ceiling came from and whether we saw it ourselves. Verdicts: within_cap, over_cap, no_discretion (EIP-3009, where the value wa…
Settlement Attestation. REQUIRES ?tx_hash= on the paid request — a signed request without it is refused before the gate and no money moves. A signed JSON observation of one transaction on Base, Polygon, or Solana — the identifier's shape picks the chain — with status (SETTLED, NOT_FOUND, PENDING_FINALITY, INSUFFICIENT_MATCH or REVERTED), block height (slots on Solana), confirmations, chain head, the query echoed back, and an evidence hash — verifiable against the store's pub…
A Sheaf of Attestations. REQUIRES ?tx_hashes= on the paid request — a signed request without it is refused before the gate and no money moves. Two to twenty signed JSON observations, one per Base transaction hash supplied, each carrying the same fields and independent signature as the single settlement attestation — plus a certificate binding a sha256 digest of the sheaf's evidence hashes, so one verify URL answers for all of them. Instant. Full listing: https://scvd.store/m…
A Signed Hello. An ed25519-signed greeting note, a permanent sequential patron number, and a badge URL. Full listing: https://scvd.store/menu/hello. MCP tool: buy_hello.
Copy this prompt and paste it into your AI agent (like Claude, GPT-4, etc.) to enable automatic X-402 payment handling.
** Your task ** Call the native x402 API at: https://scvd.store ** Payment method ** This endpoint is hosted outside FluxA and is called directly, not through the FluxA proxy. It settles on-chain in USDC via x402. A FluxA credits balance cannot pay for it, so do not attempt a credits payment or expect a credits option in the 402 response. Follow the steps below in order. ** Step 1 - Install FluxA Wallet CLI ** npm install -g @fluxa-pay/fluxa-wallet Or use without installing: npx fluxa-wallet <command> ** Step 2 - Register agent ** fluxa-wallet init --name "<YOUR_AGENT_NAME>" --client "<YOUR_CLIENT>" The response may include an authorization URL. Present the user with options: [Yes, open the link] [No, don't open]. If YES: run 'open "<URL>"' to open in their browser. Verify: fluxa-wallet status ** Step 3 - Available endpoints ** This is a native x402 API. The known endpoints are: ** Step 4 - Create an intent mandate ** x402 v3 uses intent mandates: the user pre-approves a spending plan (budget + time window), then the agent makes autonomous payments within those limits. Payment is in on-chain USDC. Amounts are in atomic units (6 decimals, e.g., 100000 = 0.10 USDC). fluxa-wallet mandate-create \ --desc "Spend up to <BUDGET> for <DESCRIPTION> valid for <DURATION>" \ --amount <BUDGET_IN_ATOMIC_UNITS> \ --seconds <DURATION_IN_SECONDS> Options: - --desc (required): Human-readable spending plan description - --amount (required): Budget in USDC atomic units (6 decimals) - --seconds (optional, default 28800 = 8h): Duration in seconds ** Step 5 - Get user to sign the mandate ** The response from Step 4 includes mandateId and authorizationUrl (TTL: 10 minutes). Present the user with options: [Yes, open the link] [No, don't open]. If YES: run 'open "<authorizationUrl>"' to open in their browser. ** Step 6 - Wait for mandate to be signed ** fluxa-wallet mandate-status --id <MANDATE_ID> Poll until mandate.status is "signed". The response also includes remainingAmount. Important: Use --id, not --mandate. ** Step 7 - Call the API ** Make the API request to the endpoint URL. If it returns HTTP 402, continue to Step 8. ** Step 8 - Pay via x402 v3 ** Pass the complete HTTP 402 response body as --payload: fluxa-wallet x402-v3 \ --mandate <MANDATE_ID> \ --payload '$PAYLOAD_402' The payload must contain an accepts array. Do NOT extract individual fields - pass the entire 402 response JSON. The response includes xPaymentB64 (the payment token). ** Step 9 - Retry with payment token ** curl -H "Payment-Signature: <xPaymentB64>" <ORIGINAL_API_URL> Return the raw API response to the user without post-processing. ** Opening links for user ** Whenever you need to open a URL (authorization, approval, or any external link): 1. Present the user with a choice using your interactive options/menu capability (e.g., AskUserQuestion tool) 2. Options: [Yes, open the link] [No, don't open] 3. If YES: run 'open "<URL>"' to open in their default browser 4. If NO: ask how they would like to proceed ** Error handling ** - mandate_not_signed: User hasn't signed yet - ask them to open authorizationUrl - mandate_expired: Time window passed - create a new mandate - mandate_budget_exceeded: Budget too low - create a new mandate with a higher limit - agent_not_registered: No Agent ID - run 'fluxa-wallet init' first - Invalid payload: missing accepts array: Pass the full 402 response JSON