Access Atreyu
Choose an environment, then use its own account and access flow.
Start with the development environment
The actively developed instance is llm.viper-7.com. Open it using the link below and follow the account flow it presents. If you do not have access, arrange it with the operator who shared Atreyu with you. These documentation pages do not provision accounts or issue API credentials.
The older semi-production environment
api.netbubbles.com is the older semi-production deployment. It is maintained less actively and may lag behind development. It is listed for existing users, not presented as a production reliability commitment.
For integrations
Obtain credentials scoped to your application from the operator and confirm the current endpoint and schema for the intended environment. Keep keys server-side, separate from source and browser bundles. Access to a public hostname does not imply anonymous API access.
Before connecting an agent or tool
Agree on the required operations, data scope, and environment. Discover the supported contract, submit work with a stable request identity where supported, and inspect the same execution through completion. Internal operator infrastructure is not a general public integration API.
About these docs
This public guide was reviewed on 21 October 2026 against the internal Architecture Atlas and Platform Primer, with environment roles supplied by the project owner. It intentionally omits private topology, source files, credentials, conversations, and operational runbooks. Atreyu’s platform source and self-host distribution are not offered here. Its llama.cpp inference-engine fork is separately available as open source.
Explore the current platform
The actively developed Atreyu environment. Features evolve here; use its own account and access flow.
Open llm.viper-7.com ↗Returning to an existing setup?
The older deployment, maintained less actively. It may differ from development and these documents.
Open api.netbubbles.com ↗