Start building on PlurisUnum with an external app and a protected runtime contract.
PlurisUnum is infrastructure for AI orchestration. Your app lives in a separate repo, your backend calls the protected PlurisUnum runtime, and the operator console helps you inspect what the infrastructure did.
PlurisUnum is in Developer Preview. Runtime access is issued manually after review, and protected routes fail closed without a signed identity bearer token.
POST https://plurisunum-core-v1.highpower.workers.dev/api/prompt/route
The console is a protected observability surface for the same runtime. It does not replace your app, and it does not grant public execution access by itself.
- Infrastructure that handles routing, consensus, verification, remediation, guardrails, and runtime telemetry inside the protected worker.
- A build-on-top platform for external applications that need an authenticated orchestration substrate.
- An operator-observable runtime with request ids, run ids, provider paths, routing strategy, latency, cost, and guardrail metadata.
- Not a place to put your application UI, workflow engine, or business logic.
- Not a public anonymous playground, open login product, or self-serve runtime dashboard.
- Not the repo where external apps should live. Builder apps must be created and deployed outside this repository.
Developer Preview with manual access review.
The public site is for onboarding, documentation, evidence labels, and access requests. It is not the public runtime.
No public self-serve login.
If you do not already have issued credentials, use the access request form on the homepage to start onboarding.
Issued access covers runtime and operator surfaces.
After approval, you receive a signed bearer token for protected developer routes and the operator console workflow.
Protected PlurisUnum routes require a signed identity bearer token. The verified identity context carries userId, orgId, and workspaceId, and tenant scope is derived from that signed context instead of caller-controlled headers.
Use the same issued token model for protected runtime routes like /api/prompt/route and protected operator routes such as /api/operator/*.
- 1. Open the homepage access form at /#access.
- 2. Submit your project name, intended use case, expected request volume, and provider needs.
- 3. Wait for manual review. Access is currently granted by the PlurisUnum team; there is no automated public signup flow.
- 4. After approval, integrate the issued signed identity token into your app backend and use the operator console for runtime inspection.
Build your product outside this repo.
PlurisUnum stays infrastructure-only. Your external application owns workflow logic, UI, persistence, and business rules. PlurisUnum owns orchestration inside the protected runtime.
Your product interface
Owns auth, workflow, and business logic
Protected orchestration runtime
OpenAI, Google, Grok, and others behind the runtime
POST https://plurisunum-core-v1.highpower.workers.dev/api/prompt/route
Authorization: Bearer <signed identity token>
Content-Type: application/json
{
"prompt": "Summarize this incident timeline in five bullets.",
"providers": ["openai", "google"],
"temperature": 0.2,
"preferenceMode": "balanced"
}{
"request_id": "af32034e-89f7-47a3-8aef-1d4e3d0109df",
"run_id": "2b6d6e8a-66d8-46d1-9588-944e7fc4130d",
"provider": "openai:gpt-4o-mini",
"routing_strategy": "balanced_single",
"latency_ms": 842,
"estimated_cost": 0.0031,
"fanout_count": 1,
"consensus_status": "not_applicable",
"guardrail_triggered": false,
"response_text": "1. Detection started at 09:02 UTC...",
"error_object": null
}- 1. Create your application in a separate repository.
- 2. Put your product UI and workflows in your app repo, not in PlurisUnum.
- 3. Put the PlurisUnum bearer token on your app backend, not in public frontend code.
- 4. Call the protected PlurisUnum runtime from your backend.
- 5. Return the answer plus request_id, run_id, strategy, and provider metadata to your UI for debugging and support.
A user asks your app to summarize an incident. Your backend sends the prompt to PlurisUnum. PlurisUnum handles provider selection and orchestration. Your app stores the result, shows the answer in the UI, and exposes the returned request id so your team can inspect the run in the operator console.
const response = await fetch(
'https://plurisunum-core-v1.highpower.workers.dev/api/prompt/route',
{
method: 'POST',
headers: {
Authorization: `Bearer ${process.env.PLURISUNUM_TOKEN}`,
'Content-Type': 'application/json'
},
body: JSON.stringify({
prompt: `Summarize this incident timeline: ${timeline}`,
providers: ['openai', 'google'],
temperature: 0.2,
preferenceMode: 'balanced'
})
}
);
const payload = await response.json();
return {
summary: payload.response_text,
requestId: payload.request_id,
runId: payload.run_id,
route: payload.routing_strategy,
provider: payload.provider,
latencyMs: payload.latency_ms
};- Open the operator console only after you have protected developer access.
- Use it to inspect routing execution, provider health, execution timelines, cost guardrail behavior, and request-specific runtime metadata.
- Match your app UI’s displayed request_id or run_id to the protected runtime inspection surfaces when debugging.
A minimal external consumer reference is included as a public documentation page. It demonstrates the separate-repo pattern, backend auth usage, request submission, response handling, and request-id telemetry display without turning this repository into an application repo.