Bring your own AI agent
Use Claude, ChatGPT, Codex, Copilot, Gemini, or a custom runtime. ITMS does not require one model vendor.
Your AI agent can work with Prophit.ai’s AI agent through governed interfaces. Connect the runtime your team already uses to documented ITMS operations: your AI agent prepares requests and delegates supported tax work, and ITMS answers with evidence-backed, reviewable results instead of pretending a person clicked through software.
1 read ITMS documentation2 select supported endpoint3 submit scoped request4 inspect result + evidence5 escalate human decisionHuman authority remains at the action boundary.Use Claude, ChatGPT, Codex, Copilot, Gemini, or a custom runtime. ITMS does not require one model vendor.
Your AI agent works through documented interfaces, schemas, credentials, permissions, and predictable error states.
Requests, responses, evidence, exceptions, and authority boundaries remain visible to the people accountable for the result.
Concrete workflows grounded in the shipped product modules. Each one returns reviewable results, and each one stops at the authority boundary that protects your operation.
Your AI agent gathers or prepares transaction inputs, runs supported calculation, reconciles expected against collected tax, surfaces exceptions, prepares filing-ready outputs, and requests your approval.
A supported filing lane is used only when it is configured and separately authorized.Explore Sales Tax Compliance →It reviews economic and physical-presence signals, approaching thresholds, and obligation status across states, then reports where filing work may be required.
Registration is not supported in ITMS; that decision and step stay with your team.Explore Sales Tax Compliance →It compares tax charged by vendors against expected tax with reason-code support, ranks variances by materiality, and prepares use tax accrual and overpayment candidates for review.
Reviewers adopt or correct candidates; the AI agent does not finalize accruals on its own.Explore Purchasing Tax Compliance →It identifies expired and expiring exemption certificates against state legal rules and your internal policies, then prepares supported renewal outreach for the affected customers.
Outreach is sent only with configured communications authority.Explore Exemption Certificate Management →It reviews purchasing or audit results, assembles evidence-linked overpayment findings, and prepares or issues supported vendor exemption certificates for purchases that were taxed in error.
Findings carry their evidence; no refund, authority, or legal outcome is guaranteed.Explore Risk & Recovery →It lines up billing, ERP or GL, tax engine, and filed-return totals, computes deltas, drafts explanations for material exceptions, and stages the run for reviewer signoff.
Prepared, reviewed, and approved states stay with people; unsafe actions remain blocked.Explore Reconciliation →It pulls entitlement-scoped analytics for the active organization and location, then summarizes exposure, readiness, and throughput with links back to the underlying work.
Summaries cite the operational data they came from instead of inventing totals.Explore Analytics & Reporting →Be clear-eyed about which part is shipped and which part is direction. The governance model is the same in both.
Over time, your AI agent should be able to hand Prophit.ai’s AI agent a whole outcome, such as preparing a period for filing review, and get back finished, evidence-backed work rather than orchestrating each call itself.
The boundaries do not loosen as that surface widens: the same plans, configuration, jurisdiction coverage, scoped credentials, evidence, and human approval points govern every delegated step. New connection surfaces will appear in the API documentation when they ship, not before.
Start with one bounded operation, then expand only where your plan, configuration, jurisdiction coverage, credentials, and review model support it.
Create the operating context an authorized workflow needs before tax work begins.
Move structured transaction data into supported workflows, surface missing fields, and inspect validation results.
Use deterministic tax rules where coverage exists and controlled assistance where a reviewable classification is appropriate.
Connect supported certificate records, exemption status, and transaction context without hiding the source evidence.
Compare source and tax records, identify variances, and route unresolved questions to the right reviewer.
Organize reviewed period data and filing evidence while keeping submission, payment, and approval authority explicit.
Apply supported rules and fail closed when coverage is unavailable. A missing rule does not become a guessed tax result.
Use configured probabilistic assistance for eligible unknown classifications, keep the result reviewable, and preserve human escalation.
The useful distinction is not whether AI is present. It is whether each step has the context, interface, evidence, and authority it needs.
Read the current documentation, schemas, supported operations, and environment requirements.
Gather the organization, location, transaction, certificate, or period context the operation requires.
Send a scoped request with the right credential and stop when validation or coverage is unavailable.
Inspect the result, evidence, warnings, exceptions, and audit context before relying on the output.
Keep filing, payment, approval, and production actions behind the separate human or system authorization they require.
ITMS is built around documented HTTP interfaces rather than a single model vendor. Download a branded starter pack for your AI agent harness, then review its authority limits before connecting credentials.
Works with any AI agent runtime
Get the pack ↓Download .mdClaude projects and AI agent workflows
Get the pack ↓Download .mdCustom GPTs and AI agent workflows
Get the pack ↓Download .mdRepository and integration work
Get the pack ↓Gemini, Copilot, and custom runtimes can start with the universal pack. The live API documentation remains authoritative.
This short local product walkthrough moves from the agent-to-agent overview through supported surfaces, deterministic and AI-assisted modes, starter packs, and the three-step authority checklist.
Choose a supported workflow and understand its request, response, error, and rate-limit behavior.
Keep secrets out of prompts, files, and logs. Limit the AI agent to the organization and operations it needs.
Inspect results and audit logs before adding broader operations or any downstream filing action.
No. The AI agent experience is a way for authorized software to work through supported ITMS operations. Natural-language reasoning can help prepare and interpret work, while the tax operation still uses documented interfaces and controls.
No. Supported deterministic rules remain the source of tax outcomes where unknown information must cause a stop. AI assistance is reserved for configured tasks where uncertainty can be disclosed and reviewed.
No. Start with the runtime your team already governs. Use the universal pack or a platform-specific starter file, then connect only the credentials and operations needed for the first workflow.
Only when the product surface, entitlement, environment, and separate action authority support it. Reading documentation or calculating tax does not silently grant filing, payment, approval, or production authority.
The supported integration surface today is the documented HTTP API plus the starter packs on this page. We do not claim protocol support we have not shipped; when a connection surface is added, it will appear in the API documentation with the same authority model.
No. Registration is not part of ITMS. An AI agent can analyze nexus exposure and approaching thresholds so your team can decide what to do about them.
We’ll map the data, endpoints, deterministic rules, AI-assisted steps, review points, and authority limits needed for a responsible integration.