Skip to main content
Source-repository links require access to the private glide-co/glide-mono repository. Request access from Glide if a source link is unavailable.
Each recipe describes a focused integration. Check its prerequisites and distinguish demo adapters from live services before connecting real funds.

curl quickstart

Bare HTTP. No SDK. Make an authorized read-only account query.

TypeScript quickstart

Thin TS wrapper around the MCP gateway. Run accounts.list and print the result.

Python quickstart

Python httpx wrapper. Run accounts.list with python src/main.py.

Agent pays vendor

Review the lifecycle example, its mock responses and the requirements for live payment verification.

Bring payments into your app

Pay your own users. Pre-create accounts, collect consent, push batch payouts, verify webhooks.

Build a connector

Scaffold, implement, and test a new connector from scratch (Stripe-shaped clone).

Build a skill

Define a manifest, consent copy and entry point. Review the example tests and data-source adapter requirements.

Embed OWS React Native

Register a wallet with a demo signer, then supply and verify your own signing backend.

x402 paid API

Pay-per-call API using @glideco/x402-facilitator. Inspect demo verification and settlement, then supply real payment dependencies.

Picking your first recipe

Not sure where to start? Pick by role:

Backend self-hoster

Start with curl quickstart to understand the wire format, then build a connector to plug in your own banking rails.

Agent author

Start with TypeScript quickstart to confirm the MCP gateway is reachable, then agent pays vendor for the payment lifecycle and its demo limitations.

Platform paying its users

Go straight to bring payments into your app for the pre-create, consent, payout and webhook path, then the Partner API reference for the exact contracts.

Contributor

Start with build a skill — it walks the same scaffold pattern in the spend-export example. Connector authors should read build a connector instead.