Choose the right API and credential
Find ShareAI API endpoints for application Auth, chat, Responses, embeddings, images, Providers, Devices and Creators, with the correct URL and credential.
On this page
Choose what you want to build. Each card opens the relevant guide, with the request format, authentication, permissions and examples you can copy.
Inference and resource-management requests use https://api.shareai.now. Application authorization uses https://auth.shareai.now, the ShareAI identity issuer. Create and manage your credentials in Console.
Builders#
Register your application, authorize an account and exchange or refresh tokens.
https://auth.shareai.now/oauth/
Application client credentials
Send messages to a model and read a complete answer or a stream of text.
POST /api/v1/chat/completions
Bearer API key or approved OAuth access token
Generate a text response with instructions and explicit conversation history.
POST /api/v1/responses
Bearer API key or approved OAuth access token
Turn text into vectors for semantic search and retrieval.
POST /api/v1/embeddings
Bearer API key or approved OAuth access token
Generate an image from a prompt with a supported image model.
POST /api/v1/images/generations
Bearer API key or approved OAuth access token
Providers#
Manage your provider model catalog and pricing.
/api/v1/console/provider
HTTP Basic: provider UUID + provider token
Read sessions and control sharing for a specific device relationship.
/api/v1/console/provider/{provider_uuid}/device-management/{device_uuid}/remote/
HTTP Basic: provider UUID + device token
Creators#
Manage your collections, model tags and model packages.
/api/v1/console/creator
HTTP Basic: creator UUID + creator token
Choose the credential for the operation#
An API key and an approved OAuth access token both use Authorization: Bearer … for inference. API keys are managed in Console. OAuth access tokens belong to an application authorization: they can expire and use the refresh-token flow. Compare scopes and permissions.
Provider, Device and Creator requests use the same public API host, with different HTTP Basic credentials. The gateway preserves each credential and Console applies its existing scopes, ownership and enabled-state checks. A provider catalog token does not grant control over a device; a device token applies only to its own provider–device relationship.
Start with a read#
Inspect your inference key, list provider models, read device sessions or list Creator collections before sending a write request.
Read an endpoint card#
Every card shows the HTTP method and complete URL. Click the URL or its copy button to copy the full address. Authentication and required scopes appear below it. Keep placeholders, model IDs and scope names exactly as documented.
Last updated September 15, 2026