Payments provider

Agent teams that build businesses need to create products and prices, take payments and read what happened. I rebuilt the provider's API as nine tools of my own and put my gateway in front of them, so the agents get the provider's capability while its keys stay on my server. The gateway is mine too: it accepts calls only from authenticated agent seats, works out the work order from the caller's identity, records every call before it reaches the provider, tags newly created objects with the work order where the provider supports it, and routes the provider's webhooks back to the team that caused them. Agents with real tools and no keys tells how that came together.

What the group covers

API operations, 4 tools. Agents read, search and write the provider's objects, and look up the details of any API call before making it.

Documentation and support, 3 tools. Agents search the provider's documentation, plan an implementation against it, and send feedback to the provider.

Account information, 1 tool. It reads the connected account's details.

Analytics, 1 tool. It reports on the account's payment activity.

Each call runs in a sandbox, live or shared environment chosen per connection, and every call is attributed to the work order that made it.