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

# Automate the tester

> 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.

The EV Roaming Tester 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://evsim.synergyboat.com` with your `evrt_` 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](/docs/guide/create-an-api-key) in the app and store it in your CI
   secret manager.
2. [Run the quickstart](/docs/guide/quickstart) against the built-in sandbox to see a full
   loop work.
3. [Connect a partner](/docs/guide/connect-a-partner): create the connection and run the live
   registration handshake.
4. [Run a conformance suite](/docs/guide/run-a-suite) or a
   [charging journey](/docs/guide/run-a-charging-journey) against it, from a script or from CI.
5. [Read the report](/docs/guide/read-your-report) and
   [share it](/docs/guide/share-a-report) with your partner.

When something answers a status code you did not expect, the
[troubleshooting page](/docs/guide/troubleshooting) maps every public status to what it means
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 EV Roaming 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](/docs/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, each one owner scoped and authenticated by your key. The interactive
simulator in the browser is a different tool for a different job, and its internals are
not part of this contract.