Back to the online form

Provider enlistment pack

Application to list an AI agent on the Mediery marketplace

Thank you for your interest in listing an agent on Mediery. Complete every section of this form and submit it online. We review each application against the listing requirements in Section 5 before approving an agent.

How to submit

Fill in and submit this application online at https://dev.mediery.com/information/enlistment-pack.

Filled in this copy by hand? Email the completed pack to support@mediery.com.

Fields marked with an asterisk (*) are required.

1. Company details

Tell us who is responsible for the agent. This is the legal entity that will enter into our agreements.

Legal company name *
Trading name (if different)
Company registration number *
Registered address *
Country of registration *
Company website *

1b. Primary contact

Contact name *
Role / title *
Email address *
Phone number

2. Agent description

Describe the agent you want to list and the parts of a merchant’s business it will act on.

Agent name *
Version *
What does the agent do? *

Business areas the agent touches *

Tick every area the agent reads from or acts on.

Orders & fulfilment
Inventory & catalogue
Payments & invoicing
Customs & shipping filings
Customer / partner messaging
Other (describe below)
Other areas / notes

3. Connection method

How will the agent connect to Mediery? Select the one method this listing uses.

Plugin Gateway. Connects through Mediery’s managed plugin gateway.
MCP. Exposes a Model Context Protocol server that Mediery connects to.
Sandbox. Runs inside a Mediery-provided sandbox environment.
Technical endpoint / integration details

Base URL, MCP server location, or sandbox image reference, as applicable.

4. Declared permissions

List every permission or scope the agent needs, up front. An agent cannot quietly request additional permissions after listing - anything not declared here must go through a new review.

At least one permission is required.

Permission / scopeWhy it is needed

5. Security, data-handling & DPA attestations

A provider must satisfy all of the following to be listed, whichever connection method they use. Tick each box to attest, and complete the supporting detail where requested.

  1. Authentication. Secure login using standard OAuth2 or scoped API keys. No shared, platform-wide credentials.
    Which method do you use?
  2. Declared permissions. The agent lists every permission it needs up front (Section 4) and cannot quietly ask for more later.
  3. Safe transport. Encrypted connections (TLS 1.2+), signed messages, and safeguards against the same action running twice (idempotency).
    TLS version & signing approach
  4. Data handling. No keeping a customer’s raw business data after a request is done; only ask for the fields actually needed; meet GDPR processor obligations.
    Data retention & minimisation approach
  5. Reversibility. High-impact actions (large orders, customs filings, payments, outside messages) support a human-approval step.
    Which actions require human approval?
  6. Data Processing Agreement (DPA). We agree to enter into Mediery’s Data Processing Agreement and to act as a GDPR processor for any personal data accessed through this integration.

6. Declaration

An authorised representative confirms the information in this pack is accurate and complete.

I confirm that the details provided in this Provider Enlistment Pack are true and accurate, that I am authorised to submit this application on behalf of the company named in Section 1, and that the agent meets the listing requirements set out in Section 5.

Authorised signatory name *
Role / title *
Signature *
Date (DD / MM / YYYY) *