DAP Foundry hub
AI agents now call outside tools as part of ordinary work. Almost none of those tools can show what they did with the data, or whether the data was current.
The product is the record. The tools are how the record is made.
Every call must state how old the data may be. A person sets the ceiling for each tool, and it is bound into the tool. No acknowledgment, no computation. A gap in our data appears as a refusal, never as silence. For the officer who never touches an agent, the audit is that record read backwards.
We attest what we collected and when we last looked.
We do not issue rulings.
A new tool publishes only after a person authorizes it.
Try it
This session
This session only. Your inputs stay in this browser.
| time | declared tolerance | ceiling | calendar age | status | refusal code |
|---|
On this public page your inputs are not stored. Each response is the caller's own copy of the record.
What compliance sees
ILLUSTRATION, not live data
| time | caller | tool | calendar collected_at | declared tolerance | status | refusal code |
|---|
The view an institution's compliance officer gets when the record is kept for them.
For agents
Four tools answer JSON: this day count and three text tools. hub.md describes each one, with every parameter, refusal code and check.
One MCP server, at https://foundry.dap.solutions/mcp, serves the same four as tools. Each answer carries the endpoint's own answer, byte for byte.
The day count costs $0.01 per computed answer, in USDC on Base under x402. A refusal is not charged. The text tools and this page are free. Paying makes the paying wallet, the amount and the time public on Base.