Docs. Soliton.

Docs

One endpoint. One decision.

You say what you want in a sentence and set the bounds you will accept. Soliton reads the chain, proposes a transaction, simulates it, checks it against your bounds and returns what it did.

Five stages at their real share of the 123 ms budget. Every fourth pass refuses, because a refusal is a normal outcome and a diagram that only shows the happy path is lying.

Ask for something.

curl https://api.soliton.uk/v1/act \
  -H "Authorization: Bearer $SOLITON_KEY" \
  -d '{
    "model": "s1-nano",
    "wallet": "7Jz4...pK9m",
    "intent": "close the SOL short if funding turns positive",
    "bounds": { "max_value_usd": 25000, "max_slippage_bps": 30 }
  }'

Get back what happened.

{
  "decision": "signed",
  "slot": 459653412,
  "signature": "4RtQ...8vXc",
  "simulated_diff": { "sol": -142.06, "usdc": 24318.40 },
  "verified_by": "s1-verify",
  "latency_ms": 118
}

Four things it can answer.

A refusal is a normal outcome, not an error. It arrives with the reason attached.

signed: The transaction simulated cleanly, passed your bounds and was submitted. The signature and the state change come back with it.
refused: S1 Verify declined. The reason names which bound it hit or what the simulation showed.
abstained: The model did not have enough information to act and said so rather than guessing.
expired: The slot moved on before the decision was ready. Nothing was sent.

Not open yet.

The API is in private beta behind the models that have not shipped. The shape above is frozen, so anything you write against it now will still run.

Ask for access

The latency, the addresses and the state change in the example response are illustrative. No Soliton API call has been served in production. What is not done.