Skip to main content

Hosted Starter Portal and Outcome Workflows

Hosted Starter provides a person-authenticated Portal for bounded workflow evaluation. It is separate from the Stripe billing portal:

  • the Hosted Starter Portal is where people sign in, manage the two seats, create and review cases, export or delete retained cases, and manage the service credential;
  • the Stripe billing portal is where the buyer views invoices, changes a payment method, and cancels renewal.

The service credential used by SDKs, plugins, HTTP clients, and MCP cannot sign a person in to the Hosted Starter Portal.

Sign in as a person​

Register with an email address so the first Portal owner can be verified:

curl -X POST https://try.getaxonflow.com/api/v1/register \
-H "Content-Type: application/json" \
-d '{"label":"my-team","email":"[email protected]"}'

Open the Hosted Portal sign-in page, enter the returned tenant_id and the same email address, then use the emailed link within 15 minutes. Each link is single-use. A replay, expired link, removed member, or revoked session is refused.

The initial person is the owner. The owner can invite one additional member or reviewer, for a total of two verified Portal people:

RoleHosted Starter authority
OwnerOwn cases, member invitations and removal, exports and deletion, service-credential rotation and revocation
MemberOwn cases and own retained-case reads
ReviewerIndependent review queue and approval or rejection, but not service-credential or member administration

A person cannot approve their own proposed action. A reviewer sees another person's case only through the review queue, not through ordinary case listing or guessed identifiers.

Service credential lifecycle​

Use the service credential for SDK, plugin, HTTP, and MCP traffic. In Settings -> Members, the owner can:

  1. inspect the credential ID, secret prefix, status, and expiry;
  2. rotate it and copy the replacement secret once;
  3. revoke it immediately; or
  4. recover a revoked credential by rotating it.

Only a one-way hash is stored. Rotation invalidates the previous secret, and revocation does not revoke the owner's person session. Reviewers and members cannot read, rotate, revoke, or recover the service credential.

Outcome workflow boundary​

The Portal's Outcome workflows page contains three typed modules:

  • FinCrime screening, for a bounded transaction and risk-fact evaluation;
  • Payment exception, for reconciling payment evidence and proposing a disposition;
  • Support refund, for checking typed order, payment, eligibility, and prior-concession facts before proposing a refund disposition.

These workflows are evaluations. Every action is a proposal or a persisted synthetic result. Hosted Starter has no adapter that can move money, retry a payment, issue a refund or credit, or write to a customer system.

The accepted limits are:

LimitHosted Starter
Verified Portal people2
Governed events1,000 per UTC calendar month
New cases100 per UTC calendar month
Retained cases100 at one time
Typed case request16 KiB maximum
Governed-event burst25 per organization per UTC minute
Primary case and audit retention30 days
Standard integration1 versioned typed JSON/API contract

Deleting a case does not restore the monthly allowance. The Portal shows the authoritative case meter and remaining allowance.

Permitted data​

Use opaque references and typed facts only: case, transaction, payment, order, customer, payee, evidence, and idempotency references; amount and currency; status and reason codes; timestamps; country codes; numeric counters; and the documented enumerated evidence values.

Do not submit:

  • names, email addresses, or contact profiles inside a case;
  • card numbers, bank-account data, or authentication material;
  • government identifiers or health data;
  • raw documents, bulk exports, or free-form customer correspondence; or
  • data whose regulation or contract requires a dedicated environment.

Unknown schema fields are rejected rather than retained. The deterministic investigator used by these three Hosted workflows does not send case content to an external model provider.

Case journey​

  1. Choose one of the three modules and create a typed case.
  2. Review the evidence fingerprint, suggested action, and available actions.
  3. Record a proposed action and rationale.
  4. When independent review is required, a reviewer approves or rejects it from the separate review queue.
  5. Record the simulated disposition and, where applicable, a synthetic provider outcome and reconciliation.
  6. Export your own retained cases or delete a case from primary storage.

An owner or member lists only their own cases. Export and deletion are owner-authorized. A deleted case and its synthetic action record leave primary storage immediately; encrypted automated backups expire within seven days.

When to use Enterprise instead​

Use a paid Enterprise proof of concept or customer-managed deployment for live financial execution, more than two people, additional integrations, higher case volume, longer retention, model-backed case processing, regulated data, customer-system writes, contractual security requirements, or a required data-residency region.

See Hosted Starter billing and activation for price, governed-event metering, renewal, cancellation, and the Stripe billing portal.