FAQ

Frequently Asked

Uncompromising clarity about credit mechanics, identity routing, and runtime responsibilities.

What exactly happens during a Core call transaction?

Your system fires a secure POST transaction payload containing your input string to the target path (e.g., /api/v1/lb-1.3). Our infrastructure cryptographically validates your header sequence. Upon successful ingestion and validation of your request, exactly 1 request unit is deducted from your profile balance before the payload is forwarded to your chosen inference provider.

Do you offer processing or output warranties?

No. LogicBasis guarantees the unyielding structural framework and independent baseline behavior of the chosen identity. The actual runtime execution quality, operational speed, and contextual memory handling depend entirely on your infrastructure setup, underlying inference model, and pipeline configurations. We define the logic; you handle the execution.

What occurs if my account request balance hits zero?

Subsequent POST payloads will instantly be blocked by our API layer, returning an explicit “Insufficient credits” response string. Your active API key remains valid and deployment configurations are preserved. You can instantly reload your request capabilities at any time through the billing dashboard.

Why are there no Creative, Emotional or Expressive Cores?

LogicBasis Cores are structural identities built on clarity, constraint and cognitive stability. Creative or expressive identities cannot maintain deterministic behavior across models, temperatures or routing setups. They drift, reshape and cannot guarantee identity integrity. Only structural identities are offered — the ones that remain stable under load, predictable under variation and architecturally sound across different inference environments.