First call in about a minute.

Get a key

Access is granted by request while the platform is in preview. You will receive a key beginning rsk_live_. It is shown once and stored hashed, so keep it somewhere you control.

Check you can reach the service

No credential needed for this one. If it answers, the platform is up.

# service state, no auth required
curl https://api.r-sym.com/status

Send your first payload

Your key goes in the Authorization header. Your provider key does not go anywhere — it stays with you.

curl https://api.r-sym.com/v1/submit \
  -H "Authorization: Bearer $RSYM_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "tool": "optimize_payload",
    "payload": "...your context..."
  }'

Read the envelope

Every response has the same shape. deliverable is what you send on to your provider. dollarsSaved is what it saved you, settled against their invoice rather than our estimate.

{
  "status": "ok",
  "requestId": "2325138bcba040e1af6e8441e4dad1c6",
  "outcome": 0,
  "deliverable": "...send this instead...",
  "dollarsSaved": 0.0000,
  "latencyMs": 0
}

Dispatch to your provider

Send deliverable where you were going to send your original context. Same endpoint, same model, same account, same key. Nothing about your provider setup changes.