# Railbed Reporting for ChatGPT and Codex

> Read payment reports, order states and webhook delivery outcomes in your assistant, with access limited to one approved business and mode.

Source: https://railbed.com/docs/openai-plugin/ · Updated: 2026-10-09 · Railbed by DeepWork developer docs

For AI assistants: the index of every docs page, with the rules for an integration, is https://railbed.com/docs/llms.txt

## What you can do

Railbed Reporting helps you understand records already in your business. Ask about a payment, summarize a period of paid payments, review recent order states or investigate failed webhook delivery. Public reporting and webhook documentation works without signing in.

This plugin uses a dedicated reporting server. It cannot create or change checkouts or payment links, return buyer payment URLs, send webhooks, change fulfilment, accept held payments, refund, transfer funds or trade. Your other Railbed integrations keep their own capabilities.

Example: Railbed Reporting server

```text
https://openai-mcp.railbed.io/mcp
```

An installed development package or custom MCP connection is separate from an approved public-directory listing.

## Connect your business

1. Install the Railbed Reporting package in your client, or add the reporting server URL as a custom remote MCP connection. Choose **OAuth or no authentication** if your client offers both, so documentation remains available without an account.
2. For account reports, follow the client's Railbed sign-in. Use the same identity you use for the dashboard. No API key or signing secret is needed.
3. Ask the assistant to connect to a business. Open its Railbed approval link, choose the business and the intended **Live** or **Test** mode, and select **Read only**. Test is for simulated records and reviewer fixtures.
4. Confirm the connection yourself, then ask the assistant to check it. It should state the business, mode and effective read access.

The existing approval page initially selects Live and Full access. Choose Read only for this plugin. Even if Full access is selected, the reporting server still refuses business changes; additional permissions do not unlock excluded tools.

Example: Codex manual connection

```bash
codex mcp add railbed-reporting --url https://openai-mcp.railbed.io/mcp
codex mcp login railbed-reporting
```

Do not add the manual entry if the installed package already supplies it. Sign-in, business approval and plugin installation are separate steps.

## Ask for a report

Example: Example requests

```text
Find the payment with reference REVIEW-PAID and explain its stored status.

Summarize paid payments on October 8, 2026 in America/New_York.
Keep currencies separate and identify missing settlement amounts.

Show my latest five orders and their stored payment and fulfilment states.

List my webhook endpoint IDs and explain the most recent failed delivery.
```

Payment and order lists are bounded pages, not account-wide totals. A payment lookup can use an exact reference filter; report results omit the stored free-form reference and description, along with buyer links, customer contacts, arbitrary merchant metadata and payout destinations. Order reports include numbers, states and totals, without item or address details. Webhook reports identify endpoints by ID and subscribed events, without receiver URLs or signing secrets.

## Understand the figures

Paid-payment summaries use the stored paid time. Give an explicit timezone and a start-inclusive, end-exclusive interval of at most 31 days. More than 10,000 matching paid attempts requires a shorter interval; the server returns no partial total.

Original order amounts stay separate for each currency. Reported token receipts are grouped by payment method, network and coin, with missing-value counts. These are paid payment attempts, not unique orders, a wallet balance or an independent on-chain audit. Test figures remain simulated. Reading a record does not contact a payment provider or refresh settlement.

A successful webhook HTTP response proves delivery, not payment settlement. A failed response provides evidence about that attempt; it does not establish the receiver's internal cause. The assistant can explain verification and retry behavior from [the webhook reference](https://railbed.com/docs/webhooks.md) without sending another request.

## Tools and access

| Purpose | Tools |
| --- | --- |
| Public reporting and webhook documentation | `railbed_docs_search`, `railbed_docs_read` |
| Sign-in and business approval | `railbed_get_profile`, `railbed_get_connection`, `railbed_connect`, `railbed_get_account` |
| Stored payments and exact summaries | `railbed_list_payments`, `railbed_get_payment`, `railbed_get_payment_summary` |
| Order states and totals | `railbed_list_orders` |
| Webhook delivery outcomes | `railbed_list_webhooks`, `railbed_list_webhook_deliveries` |

The reporting server rejects other tool names before passing a request to the account service. Its OAuth credentials are bound to this reporting endpoint. A person's current business role, the approved merchant and mode, and revocation still apply to every account read.

## Disconnect and get help

In **Developers → AI assistants**, find the connection and choose **Disconnect**. Its next account request is refused. You can also remove the app in your assistant's settings. Public documentation remains available without account access.

Contact [support](https://railbed.com/contact/) for a connection or reporting problem. The [privacy policy](https://railbed.com/privacy/) explains returned data and retention, and the [terms](https://railbed.com/terms/) apply to the integration. Never send passwords, API keys, signing secrets, card details or seed phrases in a support message or assistant conversation.