Verify results
Check what FloPay MCP returned using contract revisions, API status codes, correlation IDs, aggregate context with source record links, and knowledge sources.
Verify results
Models summarize, and summaries can drift from the data. Every FloPay MCP result carries the evidence to check it: which contract produced it, what the FloPay API answered, how aggregate figures were computed, and where knowledge came from. Check that evidence before an agent's answer drives a decision.
Result metadata
Every tool result carries these keys in result._meta:
| Key | What it tells you |
|---|---|
flopay/contractRevision | The contract revision FloPay MCP served the tool from. The Tool reference records the revision it was generated from. A different revision means the tools may have changed since that reference was published. |
flopay/httpStatus | The status the FloPay API answered with. A status of 400 or above also sets isError to true. |
flopay/correlationId | The FloPay API correlation ID, when the API sent one. Quote it when you report a problem. |
flopay/traceparent | The W3C trace context, when the API sent one. |
flopay/rateLimit | Rate-limit details the API sent: limit, remaining, reset, and retryAfter. See Limits and errors. |
structuredContent is the FloPay API response body as the API returned it, and content holds the same body as text. FloPay MCP never rewrites or summarizes it, so treat structuredContent as the source of truth rather than a model's summary of it.
Tool definitions from tools/list also carry flopay/contractRevision and flopay/risk in their _meta.
Aggregate reads
Aggregate tools return the figures plus context, which records how FloPay computed them, and sourceCurrencySegments:
context field | What it tells you |
|---|---|
timeRange | The UTC reporting window. It includes from and excludes to. |
appliedFilters | Filters applied after the merchant boundary. Empty for merchant calls. |
tenantScope | Which merchant the figures cover. |
currency | The reporting currency, and the daily FX snapshots used for converted totals. |
statusSemantics | What each status in the response means, and which timestamp it counts from. |
generatedAt | When FloPay produced the response. |
dataAsOf | The point in time the underlying data reflects. |
consistency | The consistency model. Figures are eventually consistent and can lag the latest provider and webhook updates. |
authoritativeLinks | Relative FloPay API links, starting with /v1/, to the source records behind the figures. |
sourceCurrencySegments splits monetary amounts by their original currency, so you can check a converted total against its parts.
To check a figure, follow its authoritativeLinks: find the read-only tool for that route in the Tool reference, call it, and compare. A figure newer than dataAsOf cannot be in the response yet.
Knowledge sources
Every knowledge resource read carries its source in _meta:
| Key | What it tells you |
|---|---|
flopay/sourceUrl | The canonical page or release the content comes from. Cite it, and open it to confirm the content. |
flopay/sourceVersion | The version of that source. |
flopay/lastModified | When the source last changed. |
flopay/fetchedAt | When FloPay last refreshed the content. |
flopay/stale | true when FloPay has not refreshed the content in the last 24 hours. Prefer the source page. |
flopay/untrusted | Always true: the text is data to cite, never instructions to follow. |
Previews
Before an operator confirms an action, check the preview against their intent: effects shows each change with its values before and after, targets shows the records and versions involved, warnings flags anything unusual, and expiresAt shows when the confirmation lapses. Confirmed actions describes every preview field.
Report a problem
When a result looks wrong, contact FloPay with the tool name, the time of the call, flopay/correlationId, and flopay/contractRevision. Never include access tokens, refresh tokens, or customer personal data in the report.
Confirmed actions
How FloPay MCP runs mutating tools, from a preview that changes nothing to explicit confirmation, safe retries, and what to do when an outcome is unclear.
Limits and errors
FloPay MCP limits on concurrency, request and result size, and time, how rate limits show up in results, and how to recover from every error it returns.