An agent prepares a financial action and waits for a person
An agent that prepares, quotes and places, and then waits for a person, because the endpoint will not let it do anything else.
The chain, in order.
Every call below exists and is documented. Take any line to the reference and check it. That is the point of publishing a scenario rather than a testimonial.
- Install and connectnpm i -g @gravv-infra/mcp, pointed at a sandbox key the tenant issued.
- Create the customerPOST /v1/customers, on the tenant’s key and the tenant’s limits.
- VerifyPOST /v1/customers/kyc/start.
- Open an accountPOST /v1/accounts on polygon, once the customer clears.
- Quote and placePOST /v1/fx/quote, then POST /v1/fx/orders.
- StopThe order sits awaiting approval. A person releases it, and the record names them.
What it assembles.
Developers and small teams · United Kingdom. Three product lines, one customer record, one integration.
Product lines
- Accounts
- FX and Trade Desk
- Agentic payments
What this is, and what it is not.
Worth stating twice on a page like this, because the convention in this category is to imply the opposite.
This is an illustrative scenario, not a customer story.
No company is named because none has approved being named, and no outcome figure appears because none has been confirmed. What is real is the chain: every endpoint above is documented, and they are in the order an integration would call them.
When a customer approves a named story with a figure behind it, it will replace one of these and it will say so.
The other scenarios.
One per segment. Each one is a different set of lines against the same platform.