Showmethemoney Pro

Do not require stablepay_build_payment_policy unless another workflow explicitly depends on it.

Main workflow

When the user asks to use the premium ShowMeTheMoney capability:

1. Resolve the current buyer DID from stablepay_runtime_status.
2. Call the merchant backend premium endpoint:
   • GET http://127.0.0.1:8787/execute?agent_did=<buyer_did>
3. Treat the merchant backend as the source of truth.
4. If the backend returns 200, return the protected result.
5. If the backend returns 402 Payment Required:
   • read the payment requirement from the backend response
   • prefer the returned skill_did, skill_name, price, currency, message, and payment_endpoint
   • call stablepay_pay_via_gateway
6. If payment succeeds, retry the same /execute request once.
7. If the retry still does not return 200, explain that the premium action is still locked or verification failed.

Premium action contract

Use this request for the premium action:

• method: GET
• endpoint: http://127.0.0.1:8787/execute
• required query parameter: agent_did

Optional query parameters may be used when helpful:

• q
• prompt

These optional values are forwarded to the backend as request text for the premium action.

Expected backend behavior

The backend should:

1. receive the premium request
2. verify purchase state via StablePay
3. return 402 when the user has not purchased the skill
4. return 200 only after verification succeeds
5. return a merchant-generated proof token in the premium result

Treat the backend response as the final authority.

Success criteria

A successful premium response should include a backend-generated result such as:

• protected_result.kind = merchant-generated-proof
• protected_result.proof.display_token
• access.verified_by_backend = true

This proof token is the strongest evidence that the premium capability was unlocked through backend verification, not guessed or simulated locally.

Payment rules

When payment is required:

1. Use stablepay_pay_via_gateway.
2. Use the requirement returned by the backend when present.
3. Respect local payment limits already configured in the StablePay plugin.
4. Never claim payment succeeded unless StablePay returns a successful result.
5. Retry the premium action only once after a successful payment.

What not to use as proof of access

Never treat any of the following as proof that the premium action is unlocked:

• local plugin state
• wallet existence
• DID registration alone
• local payment policy alone
• raw Solana balance checks
• a previous purchase attempt without successful backend verification

Only the merchant backend may decide that access is unlocked.

Scope limits

This skill is only for the protected premium action exposed by:

• GET /execute?agent_did=<buyer_did>

Do not treat these routes as the main premium workflow:

• /developer/revenue
• /developer/sales
• /agent/balance
• /agent/transactions

Those are debugging or operator-facing routes, not the premium capability itself.

Safety

• Never expose private keys, mnemonic material, decrypted local state, API keys, or merchant secrets.
• Never bypass backend verification.
• Never invent payment success.
• Never claim premium access is unlocked unless the backend returns success.
• Never return fabricated proof tokens.