> ## Documentation Index
> Fetch the complete documentation index at: https://docs.chargerdojo.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Automate ChargerDojo

> The workflows you can drive with an API key: connect a partner, run conformance suites and charging journeys, then read and share the graded evidence.

ChargerDojo runs your partner's OCPI implementation against the specification
and gives you a report you can forward, with the request and response behind every check.
Everything in these guides is driven the same way: an HTTPS call to
`https://chargerdojo.com` with your `cdojo_` API key.

It exists for one situation: you are mid-integration, you have a deadline, and you and
your partner disagree about whose side is wrong.

## The path

1. [Create an API key](/guide/create-an-api-key) in the app and store it in your CI
   secret manager.
2. [Run the quickstart](/guide/quickstart) against the built-in sandbox to see a full
   loop work.
3. [Connect a partner](/guide/connect-a-partner): create the connection and run the live
   registration handshake.
4. [Run a conformance suite](/guide/run-a-suite) or a
   [charging journey](/guide/run-a-charging-journey) against it, from a script or from CI.
5. [Read the report](/guide/read-your-report) and
   [share it](/guide/share-a-report) with your partner.

If you spend your day in a coding agent, [connect it](/guide/connect-a-coding-agent)
first. Asking it which OCPI version does what, or what changed between two of them,
needs no key and no account, and it is the cheapest way to find out whether any of
this is for you.

Unfamiliar vocabulary is not your fault: OCPI has a lot of it. The [glossary](/guide/glossary)
defines every term these guides use, in a sentence each.

When something answers a status code you did not expect, the
[troubleshooting page](/guide/troubleshooting) maps the statuses you will actually hit to what they mean
and, more importantly, keeps "your partner broke a rule" separate from "we did not get an
answer".

## What these guides will not claim

**A green run is not certification.** We are not the EVRoaming Foundation. A run here is
evidence, and good evidence, but if you need a certificate you need them, not us.

**A warning is not a failure.** The specification distinguishes what you must do from
what you should do, and so do we. A partner who declines a recommendation has broken no
rule, and no verdict here will say otherwise. [Read your report](/guide/read-your-report)
explains why this matters more than it sounds.

**The API is deliberately small.** The operations documented in the API reference are the
public contract, authenticated by your key, with every resource-bearing operation resolved
against that key's owner. A few reads (the suite list, the journey catalogue) are the same for
everyone. The interactive
simulator in the browser is a different tool for a different job, and its internals are
not part of this contract.