Retrieve your CLIENT-ID, USERNAME, CLIENT-SECRET, and API-KEY from Settings > Keys in the Veryfi portal
Construct the Authorization header as 'apikey USERNAME:API_KEY' and the CLIENT-ID header with your client ID
Generate an HMAC-SHA256 signature over the JSON payload and current Unix timestamp (ms) using CLIENT-SECRET; include as X-Veryfi-Request-Signature and X-Veryfi-Request-Timestamp headers
POST the invoice file (base64-encoded or as a URL) to https://api.veryfi.com/api/v8/partner/documents/
Read the structured JSON response for vendor, invoice_number, date, line_items, tax, and total fields
Known gotchas
Request signatures are valid for only 30 minutes from the timestamp; ensure server clocks are synchronized to avoid signature rejection
Both CLIENT-ID and the apikey Authorization header are required simultaneously; omitting either returns a 401
Free-tier rate limits are restrictive; check your plan's document-per-month quota before production deployment
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