SERVICEPROOFdevelopers

Agentic field service

Every capability is a REST route and an MCP tool.

ServiceProof runs field and office workflows, dispatch, work orders, inventory, purchasing and billing for field-service businesses - couriers, HVAC, plumbing, electrical, appliance repair. It was built so that a person clicking a button and a model calling a tool go through the same door. Ready for you no matter where you need to integrate.

844capabilities
4doors each
0hand-written tool defs

The rule the whole platform is built on

A capability is written once, as a C# type that declares its own name, description, required role and blast radius. The REST router, the MCP tool list, the copilot and the parity gate are all projections of that one declaration.

Door 1

REST

POST /api/v1/save_dispatch

The request record is the body. Nothing is hand-mapped.

Door 2

MCP

save_dispatch

The same record becomes the tool's JSON schema, automatically.

Door 3

Copilot

tool_use.input

The in-product assistant sees exactly the tools your key allows.

Door 4

The GUI

the same executor

The screen has no private path. It queues behind the same gate.

Anything a human can do in ServiceProof, your integration can do, too.

Point an assistant at it and walk away

ServiceProof speaks MCP natively. Give Claude, ChatGPT, Cursor or your own agent one URL and a key, and it discovers the platform by itself - the capabilities, their schemas, and this documentation.

{
  "mcpServers": {
    "riproka": {
      "url": "https://api.riproka.com/mcp",
      "headers": { "Authorization": "Bearer rka1.<your-key>" }
    }
  }
}

The model then calls list_documents and read_document to read the integrator library, search_capabilities to find the right tool, and whoami to learn what its key is actually allowed to do. You do not write a system prompt describing the API. It reads the API.

The MCP guide

Two keys, and they are deliberately not the same

tenant

Your company's key

Mint it yourself in the portal. It is scoped to your company's database and can never exceed the roles the person who owns it holds - the intersection is recomputed on every single call, so revoking somebody's role narrows their keys instantly, with no sweep and nothing to remember.

  • Expires in 90 days by default
  • Ten live keys per person
  • Revoking a membership kills its keys
Mint a key
platform

The operations key

Provisioning companies, creating users, cross-company administration. It lives in the control plane, it is held by platform operators, and it is never granted by a company administrator to themselves.

  • Separate credential, separate door
  • Cross-company by design
  • Audited against a named human
How it works

Your data is yours. That is an architecture, not a promise.

Open surface

Every capability we use is a capability you can call. There is no private API that makes our client special.

Your storage

Photos and documents can live in your own S3 bucket, your Azure account, your Drive, or a share in your building.

Nothing opaque

Workflow answers land in typed columns, not a JSON blob. If you cannot query it, we have hidden it from you.

Not the source of truth

Keep ServiceTitan or Procore as your dispatch system. ServiceProof can run the workflows silently underneath.

Reconciliation kept

Migrated records keep their original identifiers, verbatim, because your staff say those numbers out loud.

Read it all

The documentation is served as markdown to any tool that asks, and as llms.txt for models.