https://api.crevio.co/v1, the official @crevio/sdk TypeScript client, and an MCP endpoint that exposes the platform to AI agents.
The AI-native thesis: almost anything you can do with the API, you can also just ask Crevio’s agent to do over MCP — “launch a paid course”, “research my competitors and draft three posts”, “spin up a landing page”. The agent and the API share the same primitives, so you can mix scripted calls with delegated work.
Pick your path
Quickstart
Pick this if you just got an API key. Go from zero to your first successful call — and your first product — in under five minutes.
Build a custom website or checkout
Pick this if you’re a frontend or full-stack dev building your own buying experience. Use
@crevio/sdk to read products and create checkouts; payments stay on Crevio’s rails.Run an AI agent (Tasks & MCP)
Pick this if you want autonomous work, not just CRUD. Schedule Tasks (your AI workforce) or wire Crevio’s MCP into your own agent.
Generate content with AI
Pick this if you’re building content tooling — images, video, audio, web research, and social posts via metered pay-per-call endpoints.
Sync data & webhooks
Pick this if you’re integrating Crevio with another system. List and paginate resources, then react to events with signed webhooks.
Conventions & gotchas
Read this before you write code. Unwrapped params, association ids, creation order, money in cents — the rules that prevent most first-day errors.
Start here
Quickstart
Key to first call, fast.
Conventions
The request and response rules every endpoint follows.
API reference
Every endpoint, parameter, and schema — auto-generated.
MCP & agents
Let an AI agent drive Crevio.