Let your AI agent pay for x402 APIs on Canton.

STEP 1 of 2: create and fund a Canton wallet via an HTTP API. Base URL: https://pay.ftptech.xyz. This step is async: the POST returns HTTP 202 with a job id, then you GET the poll URL every 3 seconds until status is terminal ("funded" or "failed"). Each HTTP call returns quickly; the slow work happens in the background, so just keep polling. All requests/responses are JSON.

1. POST https://pay.ftptech.xyz/v1/quest/wallet/create with header `content-type: application/json` and body `{}`. Read `walletJobId` from the 202 response.
2. Poll GET https://pay.ftptech.xyz/v1/quest/wallet/result?walletJobId=<walletJobId> every 3s:
   - {"status":"pending"} -> keep polling.
   - {"ok":false,...} -> stop and report the `error`.
   - {"status":"funded",...} -> done. SAVE `walletToken`, `party`, `balanceCc`, and `secret` (the secret is the wallet's PRIVATE KEY — it IS the wallet; whoever holds it controls the funds).

Do NOT re-POST create in a loop; if you must retry, re-issue the SAME POST (the server coalesces a create retry, so it never makes a second wallet). On 429 report rate_limited; on 503 report budget_exhausted.

REPORT BACK: party + balanceCc, then a "WALLET BACKUP — SAVE THIS" section that hands your user the FULL `secret` PEM in a code block plus the restore instructions from the response's `backup` field. The wallet belongs to the USER and keeps working after this chat; delivering the secret to them here IS the backup — without it the wallet is unrecoverable. Never send the secret to any URL or tool, and if the user asks for a backup later, give them this SAME saved secret — never create a new wallet for a backup. KEEP the walletToken; you need it for step 2.

STEP 2 of 2: generate an image and settle the on-ledger payment for it from the wallet you funded in step 1. The merchant is the CanTrust image API; one call settles 0.25 CC and returns a generated image. Same base URL https://pay.ftptech.xyz and the same async pattern (the POST returns HTTP 202 with a job id, then you GET the poll URL every 3 seconds until terminal). Use the `walletToken` you saved in step 1 (it is valid for about 15 minutes, so do this promptly). Do NOT send the secret.

3. POST https://pay.ftptech.xyz/v1/quest/wallet/pay with header `content-type: application/json` and body `{"walletToken":"<walletToken from step 1>","prompt":"<describe the image you want>"}`. Read `payJobId` from the 202 response.
4. Poll GET https://pay.ftptech.xyz/v1/quest/wallet/pay-result?payJobId=<payJobId> every 3s (this step is slower, allow about 20 to 30 seconds):
   - {"status":"pending"} -> keep polling.
   - {"ok":false,...} -> stop and report the `error`.
   - {"status":"done",...} -> done. SAVE `image` (the URL of the generated image) and `updateId` (the on-ledger settlement proof).
5. (Optional) Confirm it: GET https://pay.ftptech.xyz/v1/quest/verify?updateId=<updateId> and check `valid==true`.

If a pay POST returns 404 it means wallet_not_found (the walletToken expired or was already used); 409 means already_used (re-poll your existing pay job instead of re-POSTing). Do NOT re-POST pay in a loop; the server rejects a duplicate pay, so it never makes a second transaction.

REPORT BACK to the user and LEAD with the image: render it inline as a markdown image so the user actually SEES the picture -> `![generated image](<paste the image URL here>)` -> then put the raw `image` URL on its own line, then `updateId` and verify.valid. The generated image is the whole point of this task; never omit it or replace it with a text summary. End with a wallet reminder: the step-1 wallet still holds the change and KEEPS WORKING — if the "WALLET BACKUP" block (the step-1 `secret` PEM + restore instructions) has not been delivered to the user yet, deliver it now; any later backup request means handing over that SAME saved secret, never creating a new wallet.