Can I use the API today?
The controlled pilot supports authenticated invoice-to-draft runs against a provisioned ERP.AI staging workspace. Access requires a tenant-scoped API key and staging supplier fixture. Contact the team to arrange pilot access, then follow the API reference for its supported text format and limits.
Does the demo create real ERP records?
No. The explorer changes between predefined examples in your browser. Its invoice identifiers, checks, and receipts are labeled as samples. It does not upload documents, invoke a model, connect to an ERP, create a bill, or make a payment.
What does “verified outcome” mean?
A contract defines a specific claim and the evidence required to establish it. A draft-bill contract needs both passing checks and confirmation that the intended draft exists. Verification does not imply every fact in the physical world is known, or that later approval and payment occurred.
How is this different from model routing?
Routing selects how to produce a candidate result within the task’s constraints. The outcome architecture also includes required business checks, an authorized system action where applicable, and evidence of completion. A stronger model response alone cannot confirm that a record was saved.
Must my system of record be ERP.AI?
ERP.AI provides the architectural starting point and product endorsement. Integration fit depends on the destination’s read, write, permission, and confirmation capabilities. Bring those requirements to a technical discussion so the relevant system boundaries can be evaluated.
How is pricing determined?
The commercial model separates processing costs from verified completion. Discuss expected volumes, verification requirements, routing constraints, and destination operations with the team. Charging rules, spending limits, and the treatment of failed or unresolved work belong in the commercial agreement.
What can I submit through the website?
Use the contact and support forms for non-sensitive workflow descriptions and website issues. Do not submit API keys, production credentials, invoices, financial account details, or regulated personal data.
Keep the confirmation reference shown after submission for follow-up. The privacy notice explains how contact information is handled; the trust pages cover security and integration requirements.
Missing a detail or found a problem?
Send a documentation question →