---
name: "Codex"
description: "Give Codex a goal. Make Paydro part of your product."
group: "Agents"
order: 3
---

# Paydro + Codex

With Paydro, you can start small: add a ticket shop to your website using your
public shop link, with no API credentials needed. Give Codex the relevant guide
and describe the result you want. Our examples and clear setup instructions
help you get started without learning the whole platform first. For more
involved projects, the same documentation covers registrations, event data and
connections to your existing tools.

## Try asking

- [Create a shop](/llm/set-up-event.md): “Create a draft ticket shop for our
  workshop with 50 tickets at €25 each.”
- [Check ticket inventory](/llm/manage-tickets.md): “How many tickets are still
  available for our workshop? Break it down by ticket type.”

These tasks use your authorized organizer access.

## Set up the task with AGENTS.md

Open your project in Codex and use the prompt below. Add the Paydro documentation
links and your project's test commands to `AGENTS.md` when the integration is
part of ongoing work. Codex reads these project instructions before working.

Ask for an implementation plan, then a focused change with verification. Start
with a public ticket-shop embed or an authorized, read-only API request.

[Use AGENTS.md with Codex](https://developers.openai.com/codex/guides/agents-md).

## Start with this prompt

> Add a Paydro ticket shop to this website. Read
> https://developer.paydro.com/llm/summary.md and follow the “Sell tickets on
> my website” guide. Inspect the project, ask me for any information the guide
> requires, and integrate the shop with the existing layout and design.
> Briefly explain your approach, implement it, and verify the result on
> desktop and mobile. Tell me what you changed and what you checked.

## Create a reusable Paydro skill

Working with Paydro regularly? Create a skill so your agent knows where to
find current guidance. Use its skill creator if available, or ask it to create
the skill using its supported format. Skill support and automatic activation
depend on your agent and setup.

> Use your skill creator to create a reusable `paydro` skill for Paydro
> integration and workflow questions. Configure it to activate for relevant
> Paydro requests where supported. When invoked, read
> https://paydro.com/llms.txt, follow the guides relevant to the user’s goal,
> and ask for missing required information. Support both answering questions
> and implementing requested integrations. Keep the skill concise, link to
> current documentation, and validate it using your agent’s supported skill
> format.

## Files your agent can read

Start with the summary, choose the guide for your goal and fetch only the
reference material needed for the task. These files are public and readable
without signing in.

- [Start here: goals and supported approaches](/llm/summary.md)
- [Agent documentation index](/llms.txt)
- [Complete documentation in one file](/llms-full.txt)
- [API catalog: machine-readable discovery](/.well-known/api-catalog)
- [OpenAPI: endpoints, fields and responses](/openapi/v2.json)
- [Developer guides: JSON inventory](/en-us/docs/index.json)

## More than a ticket-shop embed

[Show your events](/llm/show-events.md),
[match your branding](/llm/branding-and-language.md)
or [connect your other tools](/llm/connect-other-tools.md).
Each guide explains the supported approach and what needs organizer access.

For organizer API work, use your organization's HTTPS origin and keep authorized
credentials server-side. The developer host serves documentation. Ask your
agent to check the documented responses and verify the requested result.