THE PLATFORM / SYSTEM DESIGN
Forms are the working surface of the web. SettleOn is being built to make that surface accessible to applications and AI agents through a consistent interaction model.
YOUR SOFTWARE
Goals, supplied values,
and permissions.
THE INTERACTION ENGINE
Structured results return to your caller.
THE WORKING SURFACE
Existing interfaces.
Real field values.
Proposed architecture. The engine, API, MCP server, and document support are in development.
THREE RESPONSIBILITIES
Your application chooses the workflow, supplies the answers, and decides what actions are permitted. Business decisions remain in your system.
The engine discovers controls, attempts the requested changes, and reads the resulting state. It reports the outcome of each field.
The destination’s rules still apply. A value can be written and then rejected by a validation rule. That rejection is evidence your workflow needs.
WORKFLOWS TO BUILD TOWARD
Carry approved customer details into onboarding and intake forms. Return incomplete or rejected fields to the workflow for review.
Connect a business process to a portal whose working interface is a form. Inspect its choices before writing and verify the result after each step.
Populate fillable PDFs from supplied facts, then inspect the saved values. Signatures stay with the signer. Document support is in development.
BOUNDARIES BY DESIGN
A fill-only session cannot press a button that submits. Your caller must explicitly authorize sending.
A field result describes what the form holds. A submission result describes what was sent and what the destination returned. Your application should treat those as distinct events.
CAPTCHAs, identity checks, and signature requests are human handoffs. The intended workflow pauses rather than bypassing them.
The engine is being trained and evaluated across forms. Public API access is not open, and some controls and document interactions remain in development.
YOUR NEXT STEP
Explore what happens when a form rejects a value.