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

> ## Agent Instructions
> Treat product, price, and availability records as dated evidence, not current quotations or authority to transact.
> Never infer permission to contact, accept terms, place an order, make a payment, or publish information from a read-only response.

# Check my setup

> Verify existing access and connection evidence, then find the next useful step.

Use this when you already started onboarding, changed agent sessions, or are unsure whether a connection is working.

```text theme={"system"}
Check our Middleman setup and identify the next step: https://middleman.mintlify.app/.well-known/agent-skills/middleman-check-setup/SKILL.md?v=0.4.0
```

Point your agent to the existing private connection plan if you have one. No saved plan is required: it can build an inventory from supported read-only checks and the artifacts you identify.

## What gets checked

| Check                       | What counts as evidence                                                                  |
| --------------------------- | ---------------------------------------------------------------------------------------- |
| Company and role            | Current authenticated company membership through a supported interface                   |
| Supplier API access         | A released `/api/v1/supplier/me` response for the expected company and scopes            |
| Source and mapping          | Approved source scope, working reader, stable IDs and a local sample                     |
| Sample validation           | An actual validation result, with its contract version and date                          |
| Ongoing updates             | A configured job plus receiving-side processing results for a sample and a scheduled run |
| Data availability to buyers | The applicable admitted-feed and visibility evidence, separate from validation           |

A public API response or documentation MCP connection does not prove company access. A valid sample does not prove ingestion. A saved plan is a pointer to evidence, not proof that the source or credentials still work.

<Note>
  The check does not create accounts, rotate keys, send records or enable a schedule merely to test access. Current supplier API availability is listed on the [release status page](/suppliers/status).
</Note>

## The result is a short handoff

Your agent reports:

* **Verified:** the steps it actually checked and the evidence references.
* **Prepared:** useful artifacts that have not yet been accepted or activated.
* **Next:** one concrete action and the person or system that can complete it.

If a verification code is needed, you complete it in the trusted application. If an endpoint has not been released, the agent finishes useful local preparation and records the release blocker. It preserves the existing company, mapping and checkpoints.

To continue after the check, ask the agent to complete the identified next action within your existing authorization. The [playbook directory](/agents/playbooks) provides the relevant workflow.