Submit an agent
For bookkeeping agents, copilots, and context-aware accounting systems.
submit
Submit
Submission preview for current models and accounting agents.
Submit a model
For hosted APIs or open models evaluated on the same pack and score surface.
What to include
Name, org, model date, participant type, access tier, and output mapped to the current schema.
intake flow
How a submission is processed
Four steps, operator-run, one review batch every two weeks.
Metadata
Email with name, org, model date, participant type, access tier, and pricing reference. Missing fields are the most common reason for a delayed batch.
Dry run
One 32-row request against the public sample to validate the output schema. Failures are returned with the offending rows.
Full run
Three seeded passes on pack v1.2 with the current harness. Agents bring their own context stack; models get the shared client profile and vendor history.
Review and publish
Operator review of misses, then publication in the next roster refresh with a note on access tier and run window.
Output schema
row_idstring, from the statement
categoryone of 14 gold labels
vendor_normalizedmerchant entity string
coa_accountaccount code from target COA
splitsarray of {account, amount}
tax_treatmentdeductible · meals_50 · non_deductible · reimbursable
revertedboolean flag
confidence0–1, optional
Next batch
Intake cutoffSep 18, 2026
Review batchSep 22, 2026
Publicationnext roster refresh
Queue4 submissions in review
Runs are billed to the operator for hosted APIs at list price; self-hosted or gated models need an endpoint with 48 requests of quota.
Can I submit a fine-tune or a prompted variant?
Yes, as a separate row with its own name and model date. The base model stays in the roster; variants are marked as such.
Are prompts and harness code published?
The shared prompt, client profile, and vendor history ship with the harness notes for v1.3. Agent submissions keep their own stack private.
What if a vendor updates the model mid-batch?
The row is pinned to the model date in the metadata. A newer snapshot is a new submission and both can appear in the same roster.
Submission note: current intake is operator-reviewed. Public self-serve submission, harness packaging, and release batching are still being formalized.