Start here

AI Partner Pack

OpenAI, ChatGPT, Cursor, Lovable, Replit, and Claude — paste one feed and ship Connect, payments, top-up, inbound, ledger, and MCP.

OpenAI · ChatGPT
Cursor · Lovable · Replit · Claude
Auth · Pay · Top-up
Poll charges — no webhooks

OpenAI · ChatGPT first

Paste into ChatGPT or any OpenAI agent

Start a new chat, paste the AI guide URL (or attach llms-full.txt), then ask for Connect + PayButton. For live wallet reads, also connect MCP at https://openpaypro.space/mcp.

# Paste this into ChatGPT / OpenAI
https://openpaypro.space/api/public/docs/ai-partner

# Or long-context dump
https://openpaypro.space/llms-full.txt

# Then say:
Implement OpenPay Connect OAuth + PayButton charges for my app.
Use server-only opk_live_ keys. Poll charges. Currency OUSD.

Fastest path

Give your AI one URL

Paste /api/public/docs/ai-partner into OpenAI, ChatGPT, Cursor, Lovable, Replit, or Claude. Keys come from the Partner portal — never from the browser.

Get API keys

01

Machine-readable feeds

02

Copy-paste prompts

OpenAI · ChatGPT
You are integrating OpenPay + OpenPay Pro as a third-party partner.

Read these first (fetch the URLs):
1) https://openpaypro.space/api/public/docs/ai-partner
2) https://openpaypro.space/api/public/docs/openapi
3) https://openpaypro.space/llms.txt

Then generate production-ready code for:
- Connect OAuth (authorize → callback → POST /oauth/token → store opa_live_)
- PayButton charges (POST /charges → redirect checkout_url → poll until paid)
- Optional payouts (POST /transfers + Idempotency-Key)
- Optional Pro inbound credit (POST /api/public/openpay/inbound)

Rules:
- Server-only OPENPAY_PARTNER_API_KEY (opk_live_…) — never in the browser
- Currency is OUSD
- No partner charge webhooks — poll GET /charges/:id
- Exact-match OAuth redirect_uri

Partner API base:
https://araojncyittkahvvpdrn.supabase.co/functions/v1/partner-transfer-api

For wallet read tools in ChatGPT, also connect MCP:
https://openpaypro.space/mcp
Cursor / Claude Code
Fetch https://openpaypro.space/api/public/docs/ai-partner and
https://openpaypro.space/api/public/docs/openapi
Then implement OpenPay Partner integration in this repo:
- Server-only opk_live_ key from env
- Connect OAuth (authorize → callback → /oauth/token → store opa_live_)
- PayButton charges + poll until paid
- Optional POST /transfers with Idempotency-Key
Do not invent webhooks for charges. Do not expose the partner key to the client.
Lovable
@https://openpaypro.space/llms-full.txt
Build a merchant checkout that:
1) Creates an OpenPay charge from a server function using OPENPAY_PARTNER_API_KEY
2) Redirects the buyer to checkout_url
3) On return, polls GET /charges/:id until paid|canceled|expired
Also add a "Connect with OpenPay" button using openpy.space/connect.
Replit / Claude Projects
Use OpenPay Partner Transfer API base
https://araojncyittkahvvpdrn.supabase.co/functions/v1/partner-transfer-api
Implement auth (Connect), payments (charges), and payouts (transfers)
per https://openpaypro.space/api/public/docs/ai-partner
Secrets: OPENPAY_CLIENT_ID, OPENPAY_PARTNER_API_KEY, OPENPAY_REDIRECT_URI

03

What partners can integrate

Auth / Connect     → openpy.space/connect → POST /oauth/token → opa_live_
Payments           → POST /charges → checkout_url → poll GET /charges/:id
Payouts            → POST /transfers + Idempotency-Key
Account resolve    → GET /accounts/@user|OP…|email
OpenPay → Pro      → note pro_xfer:@user:ref → POST https://openpaypro.space/api/public/openpay/inbound
Top-up (product)   → https://openpaypro.space/topup (Pi, MoonPay, Helio, Solana Pay, Banxa, Circle…)
Reconcile          → https://openpaypro.space/api/public/ledger/entries
Agents (read-only) → https://openpaypro.space/mcp

Partner API base
https://araojncyittkahvvpdrn.supabase.co/functions/v1/partner-transfer-api

Full narrative + Node examples: /docs/openpay · /docs/api · /docs/money

04

Security rules for agents

  1. Keep opk_live_… on the server only — never VITE_ / client env.
  2. Exact-match OAuth redirect URIs in the Partner portal.
  3. Idempotency on every payout and Pro inbound credit.
  4. No partner charge webhooks — poll until paid / canceled / expired.
  5. OUSD is a ledger/network asset, not a public EVM/SPL contract.

Repo skill for Cursor agents: .agents/skills/openpay-partner-api/