Rendben

Give your coding assistant the right context.

Create a scoped API key, save it in your application environment, then give your assistant this documentation link to start the integration.

Copies the public documentation URL, not your API key.

Let an agent pay without sharing its wallet secret.

Connect to Rendben's sessionless Streamable HTTP endpoint athttps://rendben.com/mcp. Give an agent a public checkout link, or let a merchant create a payment capability with an API key. Rendben prepares unsigned transaction bytes. The agent reviews the exact terms, signs locally and submits through its own wallet or trusted Solana RPC.

{ "mcpServers": { "rendben": { "type": "http", "url": "https://rendben.com/mcp", "headers": { "Authorization": "Bearer ${RENDBEN_API_KEY}" } } } }

rendben_inspect_checkout rendben_prepare_checkout_payment rendben_create_payment_intent rendben_prepare_usdc_payment rendben_get_payment_status rendben_get_subscription_status

Never pass a seed phrase or private key.

The MCP tools do not accept wallet secrets. Use an isolated wallet, keep its signer local and enforce a per-payment or daily policy in the wallet layer.

Create a read-only key in your dashboard, keep it in your backend environment and send it as a Bearer token. This example answers the question your product actually needs: should this customer have access?

const response = await fetch( "https://rendben.com/api/v1/subscriptions?" + new URLSearchParams({ customer_reference: "google-user-48391", product_id: "prod_ciocu_basic_2026", }), { headers: { Authorization: \Bearer ${process.env.RENDBEN_API_KEY}\, }, }, ); if (!response.ok) throw new Error("Rendben verification failed"); const result = await response.json(); const hasAccess = result.hasActiveSubscription;

Never place a Rendben key in browser code, a mobile app bundle or a public repository.

Send your key on every request using the standard Authorization header.

Every public write request requires anIdempotency-Keyheader containing 8 to 128 safe characters. Repeating the same key and body returns the original response for 24 hours. Reusing a key with different JSON returns HTTP 409.

Lets an AI identify whether the human-controlled wallet step is complete and whether storefront, product and checkout preparation can continue.

curl https://rendben.com/api/v1/setup \ -H "Authorization: Bearer $RENDBEN_API_KEY"

The API reports wallet readiness but cannot access, replace or recover the wallet's seed phrase or private key.

Returns the reserved store URL, currency, public merchant details and optional logo. A new workspace returnsstorefront: null.

Reserves or updates the workspace's unique Rendben store URL. The human owner must verify the settlement wallet first. This endpoint requires a read-write key and anIdempotency-Key.

curl https://rendben.com/api/v1/storefront \ -X PUT \ -H "Authorization: Bearer $RENDBEN_API_KEY" \ -H "Content-Type: application/json" \ -H "Idempotency-Key: storefront_ciocu_v1" \ -d '{ "slug": "ciocu", "websiteUrl": "https://ciocu.app", "supportEmail": "support@ciocu.app" }'

Returns every product in the API key's workspace, including pricing and recurring billing details.

curl https://rendben.com/api/v1/products \ -H "Authorization: Bearer $RENDBEN_API_KEY"

Creates a one-time or recurring USDC product. This endpoint requires a read and write key.

Send a uniqueIdempotency-Keyfor each intended product creation.

{ "name": "Ciocu Pro", "description": "Voice, sync and monthly allowance", "returnUrl": "https://ciocu.app/billing/complete", "coverImageUrl": "https://cdn.example.com/ciocu-pro.webp", "priceUsdc": "20", "pricingModel": "recurring", "billingInterval": { "unit": "month", "count": 1 } }

Creates one resumable checkout for an active one-time product. Your customer reference and metadata are returned in webhook events.

curl https://rendben.com/api/v1/payment-intents \ -X POST \ -H "Authorization: Bearer $RENDBEN_API_KEY" \ -H "Content-Type: application/json" \ -H "Idempotency-Key: order_8f2b7f46" \ -d '{ "productId": "prod_ciocu_basic_2026", "customer": { "email": "buyer@example.com", "reference": "customer_48391" }, "metadata": { "orderId": "order_8f2b7f46" } }'

{ "paymentIntent": { "id": "pi_example", "status": "pending", "productId": "prod_ciocu_basic_2026", "customerReference": "customer_48391", "amountUsdc": "5", "merchantAmountUsdc": "4.795", "feeAmountUsdc": "0.205", "checkoutUrl": "https://yourstore.rendben.com/checkout/prod_ciocu_basic_2026?payment=pi_example", "agentPayment": { "intentId": "pi_example", "payerAccessToken": "rpa_v1_short_lived_capability", "mcpUrl": "https://rendben.com/mcp" } } }

Returns the current status, buyer wallet, Solana signature and confirmation timestamps. The API key must belong to the same workspace.

Creates a refund linked to a confirmed payment. The merchant settlement wallet must approve the returned Solana Pay transaction. The original Rendben fee is not reversed and Rendben adds no refund fee.

Send a uniqueIdempotency-Key. Multiple partial refunds are allowed, but their confirmed and pending total can never exceed the original payment.

curl https://rendben.com/api/v1/refunds \ -X POST \ -H "Authorization: Bearer $RENDBEN_API_KEY" \ -H "Content-Type: application/json" \ -H "Idempotency-Key: refund_order_8f2b7f46" \ -d '{ "paymentId": "pi_example", "percentage": "50" }'

Returns pending, processing, confirmed, expired, failed or cancelled status plus the destination wallet, Solana signature and confirmation timestamps.

Creates an opaque, resumable checkout for an active recurring product. Rendben binds the receipt email and your stable customer reference on the server, so the customer cannot change the entitlement identity at checkout.

curl https://rendben.com/api/v1/subscription-checkouts \ -X POST \ -H "Authorization: Bearer $RENDBEN_API_KEY" \ -H "Content-Type: application/json" \ -H "Idempotency-Key: subscription_google-user-48391" \ -d '{ "productId": "prod_ciocu_basic_2026", "customer": { "email": "buyer@example.com", "reference": "google-user-48391" } }'

{ "subscriptionCheckout": { "id": "sub_example", "status": "authorization_pending", "productId": "prod_ciocu_basic_2026", "customerReference": "google-user-48391", "amountUsdc": "20", "periodHours": 720, "expiresAt": "2026-08-13T13:00:00.000Z", "checkoutUrl": "https://yourstore.rendben.com/checkout/prod_ciocu_basic_2026?subscription=sub_example" } }

Do not put the Rendben API key in Ciocu's browser code. Redirect the signed-in customer to the returnedcheckoutUrl, and do not append?email=. The opaque URL already carries the server-bound identity.

Omit customer filters to list the workspace's subscriptions and read total, lifecycle and MRR summary figures. For application entitlements, filter by your stable customer reference and product ID.

{ "customerEmail": "buyer@example.com", "customerReference": "google-user-48391", "productId": "prod_ciocu_basic_2026", "status": "all", "hasActiveSubscription": true, "summary": { "total": 12, "active": 8, "pastDue": 1, "cancelPending": 1, "cancelled": 2, "entitled": 9, "mrrUsdc": "160" }, "hasMore": false, "page": 1, "pageSize": 50, "subscriptions": [ { "id": "sub_example", "productId": "prod_ciocu_basic_2026", "productName": "Ciocu Pro", "status": "active", "entitled": true, "amountUsdc": "20", "periodHours": 720, "currentPeriodEnd": "2026-08-31T12:00:00.000Z", "nextChargeAt": "2026-08-31T12:00:00.000Z" } ] }

Usesummary.activeandsummary.mrrUsdcfor merchant reporting. UsehasActiveSubscriptionto gate customer access.

Returns payment intents for a customer. The defaultstatus=paidfilter includes confirmed payments only.

{ "customerEmail": "buyer@example.com", "productId": "prod_topup", "status": "paid", "hasPaidOrder": true, "hasMore": false, "orders": [ { "id": "pi_example", "productId": "prod_topup", "productName": "Five voice credits", "status": "paid", "amountUsdc": "5", "merchantAmountUsdc": "4.795", "feeAmountUsdc": "0.205", "transactionSignature": "solana_signature", "confirmedAt": "2026-08-10T10:00:02.000Z" } ] }

- 1Recurring accessGrant access only whenhasActiveSubscriptionis true for the required product.
- 2Credits and top-upsQuery orders withstatus=paid, then store every consumed order ID so it cannot be credited twice.
- 3Cancelled subscriptionsRespectentitleduntilcurrentPeriodEnd. The customer keeps what they already paid for.
- 4Plan changesUpgrades become entitled after the atomic prorated payment confirms. Downgrades remain on the current tier through the paid period and change at renewal.
- 5Failure behaviorDo not grant new access when the API cannot be reached. Keep your last verified state for a short, deliberate grace period if your product requires continuity.
- 6Identity bindingUse your immutable user ID ascustomer.reference. Email is for receipts and can change; it must not be the primary entitlement key.

Add an HTTPS endpoint inDashboard → Webhooks. Rendben signs the exact JSON body with the secret shown once at creation. VerifyRendben-Signaturebefore parsing the event, reject timestamps older than five minutes, and deduplicate with the top-level eventid. Every envelope includesschemaVersion: 1; reject unsupported versions and ignore unknown fields within a supported version.

import { createHmac, timingSafeEqual } from "node:crypto"; const [timestampPart, signaturePart] = signatureHeader.split(","); const timestamp = timestampPart.replace("t=", ""); const received = signaturePart.replace("v1=", ""); const expected = createHmac("sha256", process.env.RENDBEN_WEBHOOK_SECRET) .update(timestamp + "." + rawRequestBody) .digest("hex"); const valid = received.length === expected.length && timingSafeEqual(Buffer.from(received), Buffer.from(expected));

Return any 2xx response within 8 seconds. Failed deliveries retry with increasing delays for up to 48 hours. The dashboard preserves every attempt and lets an owner or admin replay a delivery manually.

Subscription and order responses includepage,pageSizeandhasMore. IncreasepageuntilhasMoreis false. Customer responses are always private and are never cached.

{ "error": "customer_email or customer_reference is required." }

Read limits are shared across all V1 read endpoints for the same credential. Writes use a separate, lower ceiling of 30 requests per minute. Additional per-IP ceilings prevent rotating invalid credentials from bypassing protection. A limited response includesRateLimit-Limit,RateLimit-Remaining,RateLimit-ResetandRetry-Afterheaders.

Workspace quotas protect retained resources: 100 active products, 10 active API keys and 10 active webhook endpoints. A full quota returns409; deactivate or revoke an unused resource before retrying.

409Idempotency conflict, request in progress or workspace quota reached

500Rendben could not complete the request

Start with read-only permission. Use read and write when your application creates products, payment intents or subscription checkouts.

-

Remote MCP discovery for real-time crypto, FX, and metals market data, with x402-paid HTTP endpoints settled in USDC on Solana and Base.