Before you switch, bring the hard cases.
Five representative transactions. Equivalent inputs. A record of what worked, what differed and what still needs an answer.
Choose five cases that could change your decision.
A normal sale is useful. A disputed location, missing product, certificate boundary, partial credit or retry often reveals more. Pick the cases your team actually has to handle.
- Freeze the facts. Use the same date, addresses, product identity, nexus, certificate evidence, channel responsibilities and rounding assumptions.
- Record both outputs. Use authorized access and document each engine’s version and configuration. Leave a vendor result blank when it has not been supplied.
- Explain every difference. Separate a tax difference from a scope mismatch, missing evidence or unsupported operation. Keep unresolved results visible.
- Make the buying decision. Confirm supported coverage, integration mode, review workload and commercial terms for the product you need.
Bring your five hard transactions.
Tell us what needs to work. We’ll confirm the private evaluation path and scope for your calculation engine or compliance workflow.
Give this evaluation to your AI agent.
Let your agent inspect the evidence, choose five hard cases and show where the Sales Tax Engine or Sales Tax Compliance fits your work. Start with public synthetic examples—no account or sales call required.
- Hand over the brief. Copy it into your agent, or attach the downloaded file.
- Choose your module. Check calculations and API behavior, or trace a compliance package to its source rows.
- Connect when you’re ready. A compatible MCP client can use the module tools you authorize. Your account’s access, pricing and approval controls apply.
The brief gives instructions, not account access. Public examples are bounded demonstrations; connected tests need authorized access and may incur usage charges. See how agent connections work · Compare task rates and module plans.
Review it independently.
Use the same disclosed inputs and record failures as carefully as successful results. The public reproduction needs no account. A private API evaluation requires authorized sandbox access; the local reference environment is not a claim about every live configuration.
Publish your own findings with the pack version, date, limitations and any relationship to Prophit.ai. An untested competitor result stays untested. Continue to the API quickstart or check current pricing.
Run the public examples again.
No account or key needed. This runs the address lookup and package writer afresh with the disclosed inputs. It does not run your own transactions or submit a return.
Evidence you can inspect. Limits you can see.
The business data is synthetic. The address example uses a small official-derived historical Illinois sample. The other executions use an isolated sandbox database, disclosed inputs and the same service implementations used by the application. No customer records, filings, payments or competitor credentials were used.
The pack distinguishes local component execution from hosted API execution. The optional replay script records your own sandbox results, including failures; it does not recreate the private reference database or certify a provider. Confirm supported coverage and effective dates before evaluating a real workflow.
Sales Tax Engine · Sales Tax Compliance · API coverage contract · Current pricing