LOGICBASIS / INFRASTRUCTURE
Infrastructure
The technical foundations and implementation of LogicBasis.
A.S.0 API
The A.S.0 API provides the cognitive execution of A.S.0 for external applications.
Developers can integrate A.S.0 into their own systems without having to manage its internal Core definition or model configuration.
Usage
The interface can be used in applications that require structured processing of thoughts, questions and decisions.
| Application | Usage |
|---|---|
| Custom conversational interfaces | A.S.0 as a cognitive counterpart within a custom-developed application |
| Decision-making processes | Clarification, structuring and contextual assessment of decision-related questions |
| Work environments | Processing and organising thoughts and unresolved questions |
The integrating system is responsible for application design, user management and the storage of conversation data.
Technical Specification
| Property | Specification |
|---|---|
| System | A.S.0 |
| Model | GPT-4.1-mini |
| Planned model | GPT-6 Luna |
| Protocol | HTTPS |
| Data format | JSON |
| Language versions | German / English |
| Model configuration | Server-side |
The transition to GPT-6 Luna is scheduled for January 2027. The model used in production is determined by the relevant server configuration.
The public API does not provide a model selection option.
API-Key
API access is authenticated using a LogicBasis API key.
An API key is created in the personal account under Settings at app.logicbasis.ch.
One API key can be managed per account. The key is displayed only once when created and can subsequently be renewed or deactivated.
Access to the API requires the appropriate entitlement. The API add-on can be activated when subscribing to a Room plan or at a later date.
Authentication
The key is sent in the HTTP header with each request.
Authorization: Bearer YOUR_LOGICBASIS_API_KEYThe API key determines the associated plan and available request allowance.
Keys must not be stored or transmitted in publicly accessible client-side code. API integration should be handled by a server-side application.
Base URL
https://app.logicbasis.chEndpoints
| Language | Method | Endpoint |
|---|---|---|
| German | POST | /api/chat |
| English | POST | /api/chat-en |
The language version is determined by the endpoint used.
Request Parameters
| Field | Type | Required | Description |
|---|---|---|---|
message | string | Yes | Input text for A.S.0 |
Request Example
POST https://app.logicbasis.ch/api/chat
Authorization: Bearer YOUR_LOGICBASIS_API_KEY
Content-Type: application/json
{
"message": "Ich möchte eine Entscheidung besser verstehen."
}Response
| Field | Type | Description |
|---|---|---|
reply | string | Returned response text |
{
"reply": "..."
}The response is generated by A.S.0. Its content and length may vary depending on the input and plan.
Context
Each external request is processed without automatically carrying over conversation history.
Required context can be provided within message. A separate message array or persistent external session management is not currently provided.
JavaScript / Server
The following example shows a server-side request to the German-language A.S.0 API.
async function sendToAS0(message) {
const response = await fetch(
"https://app.logicbasis.ch/api/chat",
{
method: "POST",
headers: {
Authorization: `Bearer ${process.env.LOGICBASIS_API_KEY}`,
"Content-Type": "application/json"
},
body: JSON.stringify({ message })
}
);
const data = await response.json();
if (!response.ok) {
throw new Error(data.reply || `HTTP ${response.status}`);
}
return data.reply;
}Environment
LOGICBASIS_API_KEY=YOUR_LOGICBASIS_API_KEYThe function accepts a message string and returns the value of reply.
For the English-language version, use /api/chat-en.
The example requires a server-side JavaScript environment with fetch() and process.env.
Plans
| Plan | Room / Month | API / Month | Total / Month | Requests / Month |
|---|---|---|---|---|
| Standard | CHF 24.90 | CHF 20.00 | CHF 44.90 | 1'000 |
| Plus | CHF 49.90 | CHF 20.00 | CHF 69.90 | 5'000 |
| Enterprise | Custom | Custom | On request | Custom |
API access is provided as an add-on to the corresponding Room plan.
Request allowances are reset on the 1st of each month.
Execution Limits
| Plan | Max. Output Tokens |
|---|---|
| Standard | 520 |
| Plus | 900 |
Output limits are managed server-side and do not guarantee a particular response length.
Enterprise
Higher monthly request allowances can be agreed for Enterprise.
Pricing, capacity and access conditions are determined individually.
Enquiries: contact@logicbasis.ch
HTTP Status
| Code | Description |
|---|---|
200 | Request answered by the API route |
401 | Invalid API key |
403 | Invalid API plan |
429 | Monthly request allowance reached |
503 | Access validation or request reservation failed |
Error Response
Access validation error messages are returned in the reply field.
{
"reply": "Ungültiger API-Key."
}Current Limitations
The current implementation may return certain validation and execution errors with HTTP 200. The HTTP status alone therefore does not always confirm successful model execution.
Accepted requests count towards the monthly allowance before model execution.
Market Documentation
The technical interfaces of LogicBasis Market are documented separately.