Intelligence should be
easy to reach.
SWAY connects you to AI models through OpenRouter. Browse provider models and prices, try supported text models in the studio, or connect a server-side agent through the API. Models marked Free need no prepaid balance. Paid model usage is funded with USDC on Solana.
A small beginning.
- 01
Connect your wallet and sign the authentication message. No payment is made during sign-in.
- 02
Choose a supported free text model to start without credits. For paid models, add 5–500 USDC when checkout is available and verify the finalized payment.
- 03
Create an API key, set its spending limits, and store it as a server-side secret.
- 04
Send a text request with the selected model ID. Replace the example host with your SWAY deployment; availability of the example model can change.
The public SWAY endpoint requires your SWAY API key. Keep SWAY_API_KEY in your server environment. If you use a separate private deployment, its owner may also require a hosting access header; follow that deployment’s access instructions.
curl https://YOUR-SWAY-DOMAIN/api/chat \
-H "Authorization: Bearer $SWAY_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"model": "liquid/lfm-2.5-2.6b:free",
"messages": [{"role": "user", "content": "Hello, SWAY."}],
"max_tokens": 512
}'The response follows the OpenAI chat-completion shape with choices, usage, and a sway billing object. This service supports text-only, non-streaming requests, with up to 4,096 output tokens.
Familiar, with room to grow.
The catalog includes models with different input and output capabilities. Models marked as catalog-only cannot be used in the text studio. Check sway.chatAvailable before calling them. The sway.freeToUse flag identifies supported models that require no prepaid credits; a zero base price alone is not enough.
GET/api/modelsLive model catalog, metadata, and prices.POST/api/chatFree or paid text inference with wallet session or API key.POST/api/v1/chat/completionsCompatible route for the OpenAI client SDK.GET/api/accountYour balance, transactions, and usage metadata.POST/api/keysCreate a key with model and spending policies.DELETE/api/keys/:idImmediately revoke a project key.Send Authorization: Bearer sway_… for agent calls. Key creation, revocation, and payments require a signed-in wallet session. Use a unique requestId to help prevent duplicate inference requests.
Your wallet leads the way.
Sign-in uses a one-time message challenge. SWAY verifies the wallet’s Ed25519 signature and creates a session in an HttpOnly cookie. Your private key stays with your wallet.
Each top-up receives a unique Solana Pay reference. The checkout link specifies the amount, merchant recipient, and Circle USDC mint on Solana mainnet. Approve the real transaction in your wallet, then ask SWAY to check its confirmation.
Credits are added only after the backend verifies a finalized, successful transfer of the exact amount from your signed-in wallet. Rechecking a payment does not credit it twice.
Solana transactions, wallet addresses, amounts, and payment references are public on-chain. Wallet network fees are separate from model usage.
See the cost. Set the bounds.
The market displays provider base prices in USD per one million input and output tokens. A paid request reserves a conservative maximum against your prepaid balance before it is sent. The actual provider-reported cost is settled afterward, and unused reserved credit is released.
Supported free models need a wallet session or project key, but no SWAY credits. Free use is limited to 20 requests per wallet per 24 hours, within a shared deployment allowance of 40 per 24 hours. Shorter request quotas and OpenRouter and provider limits also apply. Requests can return 429 when any limit is reached; availability can change. Paid models and credit purchases become available separately when provider funding is ready.
There is currently no added platform fee. Your API key can restrict allowed models, set a maximum request cost, and enforce a daily budget. A key’s default limits are $1 per request and $10 per day; you can choose your own limits when creating it.
If the provider outcome cannot be verified, the request remains pending while SWAY reconciles its reserved balance. An uncertain paid outcome can pause additional paid calls for up to 24 hours. Check your account usage before retrying a request; unconfirmed holds without a provider record are released after five minutes.
402Balance too lowFor paid models, add credits or reduce the requested output.403Policy limitCheck the key’s model and budget policies.409Request or billing reviewThe request ID was used, or an uncertain provider outcome needs reconciliation.429Request limit reachedWait before retrying. Free requests have account and shared provider limits.503Service unavailableThe selected inference or payment service is temporarily unavailable.A clear picture of the path.
Prompts are sent from SWAY to OpenRouter and the selected model provider to produce a response. Standard routing follows the provider’s data policies. Choosing privacy: "zero-retention" requests providers that support zero data retention and denies data collection through OpenRouter routing; availability may be more limited.
SWAY keeps usage and billing metadata in your account history, rather than storing prompt content there. API keys are stored as SHA-256 hashes and shown in full once, at creation. Keep them in a secret store and revoke them whenever a project no longer needs access.
Wallet payments are publicly verifiable on Solana. Inference is provided by external model services. SWAY does not claim enclave execution or zero-knowledge proofs for model responses.