Solarion AI ™ · Compute Passport ™ technical system

Developers

The trust API: status resolution, verification material, passport verification and decision requests.

CompanySolarion AI ™

ProductCompute Passport ™

StatusMVP

Edition2026

IssuerSolarion AI Systems ™

Trust API v1

Resolve status. Fetch keys. Verify a passport. Ask for a decision.

Four calls cover most integrations. Status and verification material are public by design — a relying party has to be able to check a passport without an account. Decisions and the registry require an authenticated caller.

Base URL

https://solarionai.com/wp-json/compute-passport/v1

Endpoint	Purpose	Access
GET /jwks	Verification material for this issuer.	Public
GET /status/{cpid}	Live status: active, suspended, expired, retired or compromised.	Public
POST /verify	Verify a presented passport and resolve its status in one call.	Public
POST /simulate	Evaluate a demonstration request. Rate limited, nothing recorded.	Public sandbox
POST /decide	Request a decision before a material action. Writes evidence.	Portal credential
POST /token	Mint a short-lived, audience-bound runtime credential.	Portal credential
GET /passports	List governed objects with claims and status.	Portal credential
POST /passports	Issue a passport.	Operator
POST /status	Suspend, revoke, retire or restore.	Operator
GET /evidence	Read the chain and its verification state.	Portal credential
GET /bundle/{cpid}	Portable evidence bundle for one object.	Portal credential

Examples

Resolve status before acting

curl "https://solarionai.com/wp-json/compute-passport/v1/status/urn%3Acpid%3Av1%3Asolarionai-com%3At-04a48908d600%3Aagent%3A01a01e99-cd68-78c5-b59d-42eeb4650631"

Ask whether an action may proceed

curl -X POST "https://solarionai.com/wp-json/compute-passport/v1/decide" \
  -H "Content-Type: application/json" \
  -u "operator:APPLICATION-PASSWORD" \
  -d '{
    "cpid": "urn:cpid:v1:{issuer}:{tenant}:agent:{uuid}",
    "action": "case-assistance",
    "model": "gov-approved-lm-2.1",
    "region": "ca-central",
    "data_class": "protected",
    "human_approval": false
  }'

Decision response

{
  "decision": "restrict",
  "checks": [ { "id": "approval", "result": "fail", "detail": "…" } ],
  "obligations": [ "log_evidence", "human_approval", "escalate_to_sponsor", "minimize_data" ],
  "evidence": { "seq": 42, "hash": "9f2c…" }
}

Authenticate server-to-server calls with a WordPress application password over TLS. Browser callers use a REST nonce. Both are stand-ins for the mutual TLS and workload identity federation a production deployment would use.

Integration order

Register the object and its sponsor. Nothing acts without a named owner.
Fetch the JWKS once and cache it. Refresh on key rotation.
Verify the presented passport locally, then resolve status online.
Call /decide before any material action, and apply the obligations returned.
Acknowledge revocation, and record the acknowledgement. Unacknowledged revocation is not containment.

Interface stability

Reference API for evaluation. Interfaces are unversioned beyond v1 and subject to change.