High-Level Flow

Qwery's workflow is designed for efficiency, dividing responsibilities between providers, consumers, and the platform:

1. Provider integrates Qwery SDK into their API.

2. Qwery issues:

   • provider keys

   • revenue wallet

   • proxy endpoint: https://api.qwery.xyz/v1/<slug>

3. Consumer/agent:

   • pays in USDC to Qwery escrow

   • calls proxy with tx reference

4. Qwery:

   • verifies payment on Solana

   • proxies the call

   • executes revenue split

   • returns response + onchain receipt

Payment Flow: User → API Server → Facilitator → Solana Blockchain

Step-by-Step:

1. User requests paid resource

2. API server calls /create-payment on facilitator

3. Facilitator returns unsigned Solana transaction

4. User signs transaction with their wallet (Phantom, etc.)

5. API server calls /settle with signed transaction

6. Facilitator co-signs, pays fees, submits to blockchain

7. Solana confirms in ~400ms

8. API server grants user access

Timing:

• Payment creation: ~200ms

• User signing: ~2-5s (wallet interaction)

• Settlement: ~800ms (blockchain confirmation)

• Total: ~3-6 seconds