Replies to support conversations
A customer opens a conversation with your business in PulseChat. Your system can read it and reply. Your business cannot start these conversations.
Developer services
Build on the 1StopTek ecosystem.
Integrate communication, AI and data infrastructure into your applications through 1StopTek developer services.
1st AI Platform API
In testingA versioned HTTPS API for chat completions, streaming, structured output and embeddings, served by the platform 1StopTek operates.
Restricted testing
| Capability | Status | Details |
|---|---|---|
| Chat completions | In testing | POST /api/v1/chat/completions with system, user and assistant messages; temperature, top_p, max_tokens and stop. |
| Streaming | In testing | Server-sent events (stream: true): chat.completion.chunk events, then data: [DONE]. |
| Structured output | In testing | response_format json_object or json_schema; the result is validated against your schema. Not combinable with streaming. |
| Embeddings | In testing | POST /api/v1/embeddings, up to 64 inputs of up to 8,000 characters each. |
| Model discovery | In testing | GET /api/v1/models lists each model with its capabilities, context window and output limit. |
| Usage API | In testing | GET /api/v1/usage returns a project's daily token counts and month-to-date totals. |
| Document retrieval (RAG) | Planned | Implemented inside Eurylie with citations; not yet exposed on the Developer API. |
| Tool and function calling | Planned | Requests that use tools are rejected with an explicit error, never silently ignored. |
| Image and audio input | Not supported | Text only. Non-text content is rejected with unsupported_content_type. |
The platform serves open-weight models on its own inference hardware. GET /api/v1/models is the authoritative list for each environment: every entry states its capabilities, context window and maximum output tokens.
Throughput and latency have not been benchmarked on the production inference hardware yet. We will publish measured figures, not targets.
Safety Layer
APIs and documentation
The Developer API is HTTPS and JSON, with an OpenAPI 3.1 description generated from the same contract the server is tested against.
| URL | ||
|---|---|---|
| Staging (testing) | https://platform-api-staging.1stoptek.com | Planned host, not online yet. Invited testers only; no model is connected yet |
| Production | https://api.1stoptek.com | Not open yet · live keys (1stai_live_…) only |
Send your project API key as a bearer token: Authorization: Bearer 1stai_test_…. Call the API from your server only; never ship a key to a browser or mobile app.
Restricted testing
export FIRSTAI_BASE_URL=https://platform-api-staging.1stoptek.com
export FIRSTAI_API_KEY=1stai_test_... # from the developer consolecurl -sS "$FIRSTAI_BASE_URL/api/v1/chat/completions" \
-H "Authorization: Bearer $FIRSTAI_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"messages": [
{"role": "system", "content": "You answer in one sentence."},
{"role": "user", "content": "What is an API key?"}
],
"max_tokens": 120
}'curl -sS -N "$FIRSTAI_BASE_URL/api/v1/chat/completions" \
-H "Authorization: Bearer $FIRSTAI_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"messages": [{"role": "user", "content": "Count from one to five."}],
"max_tokens": 60,
"stream": true
}'
# data: {"object":"chat.completion.chunk","choices":[{"delta":{"content":"One"},...}]}
# ...
# data: [DONE]curl -sS "$FIRSTAI_BASE_URL/api/v1/embeddings" \
-H "Authorization: Bearer $FIRSTAI_API_KEY" \
-H "Content-Type: application/json" \
-d '{"input": ["first document", "second document"]}'curl -sS "$FIRSTAI_BASE_URL/api/v1/chat/completions" \
-H "Authorization: Bearer $FIRSTAI_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"messages": [{"role": "user", "content": "Extract: Berlin is the capital of Germany."}],
"max_tokens": 120,
"response_format": {
"type": "json_schema",
"json_schema": {
"name": "fact",
"schema": {
"type": "object",
"properties": {"city": {"type": "string"}, "country": {"type": "string"}},
"required": ["city", "country"]
}
}
}
}'import json, os, urllib.request
req = urllib.request.Request(
os.environ["FIRSTAI_BASE_URL"] + "/api/v1/chat/completions",
method="POST",
headers={
"Authorization": "Bearer " + os.environ["FIRSTAI_API_KEY"],
"Content-Type": "application/json",
},
data=json.dumps({
"messages": [{"role": "user", "content": "Say hello."}],
"max_tokens": 60,
}).encode(),
)
try:
with urllib.request.urlopen(req, timeout=120) as resp:
body = json.load(resp)
print(body["choices"][0]["message"]["content"])
print(body["usage"])
except urllib.error.HTTPError as err:
error = json.load(err)["error"]
print(err.code, error["type"], error["code"], error["request_id"])const res = await fetch(`${process.env.FIRSTAI_BASE_URL}/api/v1/chat/completions`, {
method: "POST",
headers: {
Authorization: `Bearer ${process.env.FIRSTAI_API_KEY}`,
"Content-Type": "application/json",
},
body: JSON.stringify({
messages: [{ role: "user", content: "Say hello." }],
max_tokens: 60,
}),
});
const body = await res.json();
if (!res.ok) {
const { type, code, request_id } = body.error;
throw new Error(`${res.status} ${type}/${code} (request ${request_id})`);
}
console.log(body.choices[0].message.content, body.usage);There is no separate SDK package yet. The examples use plain HTTP; because the request and response shapes follow the widely used chat-completions format, many existing client libraries work by changing the base URL. We document only clients we have tested.
Each project has a requests-per-minute bucket and each organization a monthly token allowance, set by its tier. Every response reports the remaining requests in X-RateLimit-Limit-Requests and X-RateLimit-Remaining-Requests; a 429 carries Retry-After.
| Tier | Requests per minute (per project) | Tokens per month (per organization) | Max output tokens | Concurrent streams |
|---|---|---|---|---|
| sandbox | 20 | 500,000 | 1,024 | 2 |
| developer | 120 | 10,000,000 | 4,096 | 10 |
| scale | 600 | 100,000,000 | 4,096 | 50 |
| enterprise | 3,000 | 1,000,000,000 | 4,096 | 200 |
New organizations start in sandbox. Tiers are limits, not prices; higher tiers are assigned after review.
Every error has the same JSON shape. Branch on type; log request_id when you contact support. Messages never contain your prompt.
{"error": {"type": "rate_limit_error", "code": "rate_limited",
"message": "project limit of 20 requests per minute reached",
"param": null, "request_id": "req_…", "retry_after_seconds": 3}}| HTTP | type | Typical codes |
|---|---|---|
| 400 | invalid_request_error | invalid_messages, unsupported_parameter, context_length_exceeded |
| 401 | authentication_error | invalid_api_key |
| 402 | quota_exceeded_error | monthly_quota_exceeded, spending_limit_reached |
| 403 | permission_error | forbidden, organization_suspended |
| 404 | not_found_error | model_not_found |
| 409 | conflict_error | key_limit_reached, project_archived |
| 422 | safety_error | safety_refused |
| 429 | rate_limit_error | rate_limited, too_many_streams |
| 502 / 504 | model_error | model_error, model_timeout, invalid_structured_output |
| 503 | service_unavailable_error | model_unavailable, billing_unavailable |
Retries
Versioning
Developer account and API keys
One 1StopTek account signs you in. Organizations, projects and keys belong to the platform; the console manages them for you.
01
Create account
Testing is by invitation: ask for tester access, then sign up with email and password.
02
Verify email
Follow the link we send. Unverified accounts cannot reach the console.
03
Create organization
You become its owner. A Default project is created with it.
04
Generate API key
Choose name, scopes and optional expiry. The full key is shown once.
05
Make first request
Use the quick start with your key.
06
View usage and costs
Tokens, requests and estimated charges per project and key.
Website assistants
The technical details behind the guided setup in the console.
Example only: website assistants aren't available to customers yet.
The code identifies the assistant with its public assistant id. It contains no key. The assistant accepts browser requests only from the exact https origins of websites whose ownership was confirmed. A program outside a browser can imitate an origin, so per-visitor limits, per-assistant limits and your spending limit apply as well.
<script src="https://{widget-host}/widget/v1/agent.js" data-agent="agt_…" async></script>The widget host isn't decided yet; the code shows a placeholder.
The stable path follows compatible widget updates. To pin one release, use the versioned path and the integrity hash published in the widget's manifest.json.
<script src="https://{widget-host}/widget/v1/{version}/agent.js"
integrity="sha384-…" crossorigin="anonymous"
data-agent="agt_…" async></script>Options
Server-to-server (Advanced settings)
Usage and billing
Metering happens on the server, per request, at the moment a request completes. The console shows exactly what the platform recorded.
Alert threshold
Hard spending limit
Requests in flight
If usage cannot be checked
API v1 · contract 0b847d90d1
PulseChat Business API
Implemented, not enabledVerified businesses will connect their shop, ticketing or booking system to PulseChat: to answer the support conversations their customers start, and to send transactional updates to customers who opted in.
The business API is implemented and tested, but it is not enabled yet and has no external developers. Setup, the sandbox and live access are not open; this page will say when that changes.
A customer opens a conversation with your business in PulseChat. Your system can read it and reply. Your business cannot start these conversations.
Order, service, appointment and account updates, sent with templates PulseChat has approved, only to customers who opted in to updates from your business. Customers can withdraw at any time. The final opt-in model is under legal review.
Your system sees a customer only through a reference specific to your business, not their phone number, PulseChat ID or name. That is not anonymity: customers can still share personal details in their own messages.
Guided setup and the developer documentation will be published once PulseChat opens the API. If you want to be considered for the pilot, get in touch.
Account and service updates, and replies to support conversations your customers start.
Confirmations, reminders, changes and cancellations.
Order and support messages between a marketplace and its own customers, without sharing customers' phone numbers.
1Stop DataHub
PlannedOne place to manage the 1StopTek integrations your organization uses — applications, credentials, teams and usage.
One account. Multiple products. One platform.
Developers and organizations will manage supported 1StopTek integrations from one environment. The control-plane foundations underneath — identity, roles and permissions, entitlements, auditing — are in active development; DataHub is the planned product on top of them.
Developer services
For organizations managing advertising and commercial 1StopTek services.
Go to 1StopTek Business →For developers integrating 1StopTek technology into applications and services.
The planned technical management layer connecting applications, credentials, permissions, usage and supported ecosystem services.
Developer access to the PulseChat Business API, the 1st AI Platform API and 1Stop DataHub is being prepared. If you are a developer, a business or an integration partner, talk to us about early access, API integrations, enterprise integrations and partnerships.