Skip to main content
ChargerDojo tells you where your OCPI implementation departs from the specification, and shows you the exchange that proves it. You can drive all of it in the browser; these pages are for the parts you want to automate. The end of a run looks like this:
Each of those two failures names the check, the rule it broke, and the request and response that produced it. The three warnings are separate on purpose: they diverge from something the spec only recommends, so they never fail a build. total is passed + failed + unobservable; warned is counted separately and overlaps the others, so it is not a fourth bucket.

​
Start here

What is free

The sandbox, the simulator and the MCP server cost nothing. Where the paid line falls, and why.

Quickstart

One conformance run against the sandbox from the command line, start to verdict. Needs an API key.

Connect a coding agent

Ask OCPI questions from Claude Code, Codex or Cursor. The question half needs no account.

Connect a partner

Point it at a real endpoint and run the suite against that instead.

Read your report

What a failure is telling you, and what to change.

Run a charging journey

Drive a full charging story over time and watch it live.

Plans and pricing

What each plan costs, and the capability behind every line of the table.

Create an API key

Needed once, before the API or your own account’s data works from a terminal.

API reference

Every public operation, its authentication, and the response envelope.

​
What is public

Only the operations in the API reference section are the public API. Everything else the application does, including the interactive simulator, entity editing, and account and key management, is browser functionality, not part of the automated contract.