Create a Treasury Prime person or business entity via the KYC API, submitting PII fields including SSN or EIN, date of birth, and address in the required format
Poll the KYC status endpoint; if status is pending_documents, upload identity documents (government ID, proof of address) using the document upload endpoint with the correct document type enum
If status transitions to manual_review, implement a webhook handler for the kyc.updated event that alerts your onboarding team and pauses account activation until the review resolves
On kyc.approved, call the account creation endpoint to open the deposit account linked to the approved entity; capture the account and routing numbers returned in the response
Configure account-level controls (transaction limits, allowed transfer types) via the account controls endpoint before exposing the account to the end customer
Handle kyc.denied by triggering an adverse action notice flow with the denial reason mapped to a customer-facing explanation; do not expose raw KYC denial codes to end users
Known gotchas
Treasury Prime KYC decisions are made by the partner bank, not Treasury Prime itself; the review timeline and document requirements vary by bank partner — check the partner-specific documentation
Document image quality failures cause silent kyc.updated events with a sub-status rather than a top-level rejection; inspect the full status object, not just the top-level status field
Opening an account before KYC is approved returns an error; there is no way to pre-create the account and activate it later — the approved entity record must exist first
Give your agent this knowledge — and 200+ more routes
One MCP install gives any agent live access to the full route map, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp