Your agent can call ax1om · scoring is live over MCP, free tier included.Start freeAlready have an account?

Twelve fixes from a readiness walk of the console

Bug fixDashboard

A walk of app.ax1om.ai as a new customer, ahead of a design-partner evaluation, surfaced a dozen defects on the first-run path. All shipped the same week.

  • The first “Create score” click did nothing. A divergence notice rendered above the button row on blur and moved the button out from under the pointer. The notice now renders below the row. The notice was also wrong: a date the wizard auto-picked because the template supplied none is no longer reported as a change you made.
  • The wizard keeps a success date that names the current entity, whoever chose it, instead of replacing a template’s date with the first date field it found.
  • Success criteria read back as the person wrote them, and the “Inherited from Score” block on Review and Train uses the same formatter and tokens as the card below it.
  • The demo banner covers every step of the wizard and the Scoring API page, not only step one.
  • The per-record “why” row prints one shape, field: value (lift), instead of three grammars in one list, and a factor with neither a value nor a lift is counted under the list rather than hidden.
  • An abandoned CSV import no longer leaves a permanent empty source. A draft card offers Resume import and Delete, and nothing mid-build can be deleted.
  • Revoking the scoring key you just minted closes its reveal panel. A failed read of the agent-key list keeps the list and the mint action on screen with a Retry, instead of replacing the section with an error line.
  • The one-time key reveal uses one wording on every surface.