Call the ResolveAddress endpoint with a freeform or structured address to receive a validated, standardized address and geocoordinates
Inspect the ResolutionQuality field in the response to determine whether the address resolved to a rooftop, street, or zip-code-level match
Retrieve the current nexus declarations for the company by GETting the Nexus endpoint filtered by company ID
Add a new nexus declaration by POSTing to the Nexus endpoint with the country, region, and nexus type (sales, seller use, or marketplace facilitator)
After nexus changes, run a test transaction against an address in the newly declared region to confirm tax is now being calculated for that jurisdiction
Remove stale nexus declarations by sending a DELETE to the Nexus endpoint for the specific nexus record ID
Known gotchas
A low ResolutionQuality such as a zip-code-only match can cause Avalara to assign an incorrect jurisdiction, leading to wrong tax rates; always surface unresolved addresses for manual review
Nexus declarations take effect immediately upon save; incorrectly adding a nexus can cause tax to be charged in jurisdictions where the business has no actual obligation
Economic nexus thresholds (based on sales volume) are not automatically tracked by Avalara; the integration must implement its own threshold monitoring and trigger nexus registration separately
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