# ServiceProof > Field and office workflows for service businesses - as an API, an MCP server, and a record of the work you own. ServiceProof runs field and office workflows, dispatch, work orders, inventory, purchasing and billing for field-service businesses - couriers, HVAC, plumbing, electrical, appliance repair. ## The one thing worth knowing Every capability is written once and projected onto four doors: a REST route, an MCP tool, the in-product copilot, and the GUI. They are generated from the same declaration, so a tool and a route can never describe the same capability differently. There are 844 capabilities and every one of them is reachable from all four. ## Connect over MCP - Endpoint: https://api.riproka.com/mcp - Transport: Streamable HTTP (POST) - Auth: `Authorization: Bearer rka1..` - Protected-resource metadata: https://api.riproka.com/.well-known/oauth-protected-resource Once connected, call these before anything else. They are how you learn this platform rather than being told about it: - `whoami` - the company you are acting in and the roles you hold - `search_capabilities` - find a capability by intent, not by name - `list_documents` - the published integrator library - `read_document` - one document, as markdown ## Getting a credential An API key belongs to one person's membership of one company. A company administrator mints their own at https://portal.riproka.com/api-keys. A key can never out-scope the person who owns it: the scope is intersected with their roles on every call, so revoking a role narrows every key they hold immediately. Platform administration - provisioning companies and users - is a separate credential held by platform operators, not by customers. ## Reading the documentation - Human documentation: https://dev.riproka.com/docs - MCP guide: https://dev.riproka.com/mcp - Quickstart: https://dev.riproka.com/quickstart The library is also readable programmatically through `list_documents` and `read_document` over MCP, which is the better route for a model - it needs no session and returns markdown rather than HTML. ## Notes for agents - Everything is `POST /api/v1/{capability_name}` with a flat JSON body. No other verbs. - Field names are camelCase. Every instant is UTC with a trailing `Z`. - Your tool list is your permissions rendered. A capability you cannot call is not shown to you, so do not plan work around one you cannot see. - Destructive capabilities are withheld from unattended callers entirely. - A capability carrying a confirmation prompt expects that prompt to reach a human. Do not answer it on their behalf. ## Contact https://dev.riproka.com (alias: https://dev.serviceproof.net)