New: connect your AI to RevCore, or build on our API

Your business runs on RevCore: every lead, job, estimate, and payment. Starting today, Scale plans can open that data up, safely, in two ways. Point your AI assistant at your account and just ask it things, or build your own integration on a public REST API. Everything below lives in the developer docs, which are the source of truth.

Connect your AI assistant

Most contractors will never write a line of code, and they shouldn't have to. RevCore ships an MCP server with 15 tools, so Claude, Cursor, Viktor, or any MCP-capable assistant can work with your own account. Ask what's sitting in your pipeline, have it draft an estimate, or get a summary of this week's appointments, all from a chat window. Setup takes a few minutes with the Connect your AI guide.

The docs themselves are AI-readable too. We publish them in llms.txt form, so an AI agent can read the developer documentation directly instead of guessing.

Or build your own integration

If you have a developer, or you are one, the REST API at /api/v1 covers clients, leads, jobs, tasks, estimates, invoices, payments, appointments, the catalog and price book, and your team. Keys are self-serve in Settings, with separate test and live keys and 21 granular permission scopes, so a key gets exactly the access it needs and nothing more. There's an interactive API reference where you can try every endpoint in the browser, plus an OpenAPI 3.1 spec.

Signed webhooks round it out: 14 event types, signed with Standard Webhooks signatures and retried automatically, so your integration hears about new leads and paid invoices the moment they happen.

Safe by design

We drew the safety lines on purpose. The API can create and update clients, leads, jobs, tasks, draft estimates, appointments, and catalog items. Invoices and payments are read-only, so nothing can move money through an API key. Cost and margin data stays hidden unless a key explicitly holds the financials scope. Rate limits are published, and the API is versioned in the path, so changes within a version are additive and what you build keeps working.