Register at developer.equifax.com and provision the Consumer Credit Reports product; obtain OAuth 2.0 client_id and client_secret
POST to the Equifax /oauth/token endpoint with grant_type=client_credentials and the credit-reports scope to receive an access_token
Submit a consumer credit inquiry POST request to the credit reports API endpoint with the borrower's name, address, SSN, and date of birth, specifying the report type and desired add-ons in the request body
Parse the JSON response: extract the Equifax credit score, tradeline array (creditor names, balances, payment history), inquiry list, public records, and any collections
Feed parsed values into your automated underwriting system (AUS) — map Equifax tradeline fields to the loan-level fields required by Fannie Mae DU or Freddie Mac LPA if submitting for GSE review
Handle a 'no hit' (no file found) response as a distinct outcome from an error: a thin-file consumer with no Equifax record requires a separate decisioning path
Known gotchas
The Equifax Consumer Credit JSON API uses OAuth 2.0 with client-credentials grant — there is no session-based or API-key-only authentication in the current production API; legacy integrations using older auth patterns must be migrated
Production access is IP-restricted; multi-region deployments require each egress IP to be individually allowlisted with Equifax before any production calls succeed
Score models available in the response depend on your contract — the Equifax Risk Score and VantageScore may both be available, but FICO Score access requires a separate FICO licensing arrangement
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