Embeddings API Quickstart Guide

Authentication

Access the API using a unique API key generated from your account dashboard. Include this key in the Authorization header of every request using the Bearer scheme. The base URL for all endpoints is https://api.embeddingapis.com/v1. This URL works with the official OpenAI SDKs and any client configured for OpenAI-compatible services. Ensure your key is kept secure, as it grants access to your prepaid credits.

Each account is limited to one active key, which can be regenerated at any time. Regenerating the key immediately revokes the previous one, so update your configuration promptly.

The Chat Completions Endpoint

Send text prompts to the POST /v1/chat/completions endpoint. The API serves a single uncensored model identified by the ID uncensored. This model is an open-weight LLM tuned to answer without content refusals for lawful adult, fictional, or security-research topics. It processes text in and outputs text, making it ideal for post-processing, summarization, or extraction steps in your pipeline.

Structure your request with a messages array containing your system and user prompts. The API returns a JSON response containing the generated text.

Copycurl https://api.embeddingapis.com/v1/chat/completions \
  -H "Authorization: Bearer $API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "model": "uncensored",
    "messages": [{"role": "user", "content": "Write a blunt product review of a cheap VPN."}]
  }'

Python SDK Integration

Use the official OpenAI Python library to interact with the API. Set the base_url to our endpoint and provide your API key. This approach allows you to leverage existing client code with minimal changes. The client handles serialization and network requests, returning structured responses that you can parse for your application logic.

Ensure you are using a recent version of the SDK to support all features, including streaming and tool calling. The model ID remains uncensored when invoking completions.

Copyfrom openai import OpenAI

client = OpenAI(base_url="https://api.embeddingapis.com/v1", api_key="YOUR_KEY")

resp = client.chat.completions.create(
    model="uncensored",
    messages=[{"role": "user", "content": "Summarise this thread without softening it."}],
)
print(resp.choices[0].message.content)

Node SDK Integration

For JavaScript or TypeScript environments, use the OpenAI Node.js SDK. Configure the client with the correct base URL and API key. This setup ensures compatibility with your existing Node-based pipelines. The SDK manages the connection to the POST /v1/chat/completions endpoint, allowing you to send prompts and receive text completions efficiently.

This integration is suitable for server-side text processing, such as generating captions, scripts, or extracting data from large text blocks.

Copyimport OpenAI from "openai";

const client = new OpenAI({ baseURL: "https://api.embeddingapis.com/v1", apiKey: process.env.API_KEY });

const resp = await client.chat.completions.create({
  model: "uncensored",
  messages: [{ role: "user", content: "Draft a villain monologue for my game." }],
});
console.log(resp.choices[0].message.content);

Streaming Responses

For low-latency applications, enable streaming by setting stream: true in your request. The API returns a Server-Sent Events (SSE) stream, delivering tokens as they are generated. This is particularly useful for real-time user interfaces or when processing long texts where immediate feedback is valuable.

Parse the SSE stream to handle partial responses. The uncensored model supports this mode, allowing you to react to content as it is produced without waiting for the entire completion.

Copystream = client.chat.completions.create(
    model="uncensored",
    messages=[{"role": "user", "content": "Tell the story in second person."}],
    stream=True,
)
for chunk in stream:
    if chunk.choices and chunk.choices[0].delta.content:
        print(chunk.choices[0].delta.content, end="", flush=True)

Limits, Errors, and Context Window

The context window supports 100,000 tokens for both prompt and completion combined. Requests exceeding the 8 MB body limit or the rate limit of 300 requests per minute will fail. Authentication errors return a 401 status if the key is invalid. When prepaid credit is exhausted, requests fail because no credits remain to cover the token usage. A 429 status indicates rate limit exhaustion.

A hard content limit always applies: requests containing sexual content involving minors are blocked, regardless of other settings. All other lawful adult content is processed without refusal.