Checking runtimeSign in
PhillNet developer platform
One governed API for research, agents, media, memory, and visible work.
Build against the same in-house intelligence used by the PhillNet workspace. Start with an OpenAI-compatible route, then add project memory, evidence, multimodal jobs, and supervised agents without changing identity or billing systems.
Scoped keysPer-app usageApproval-gated tools
QuickstartFirst response
Runtime unavailablecurl https://phillnet.com/api/v1/responses \
-H "Authorization: Bearer $PHILLNET_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"model": "phillnet-3-world-omni",
"input": "Inspect this research question with cited evidence",
"reasoning_effort": "high"
}'API surface
Start small. Add capability without adding another account system.
Every request remains tied to an owner, app, key, scope, quota, trace, and rate policy.
Deep research
Bounded web search, source evidence, file context, and traceable synthesis.
Supervised agents
Planner, researcher, builder, and verifier lanes with approval-gated writes.
Image and vision
Generate, inspect, retain, and deliver project-owned visual artifacts.
Voice and video
Route audio and video jobs through the same identity and usage ledger.
MCP and tools
Expose allowlisted tools while preserving user scope, trace IDs, and policy.
Apps and callbacks
Register HTTPS callbacks, isolate environments, and track app events.
MethodEndpointPurposeRequired scope
POST
/v1/responsesUnified text, research, files, and tool routescore:readPOST
/v1/chat/completionsOpenAI-compatible chat migration pathcore:readPOST
/v1/images/generationsProject-scoped image generationagent:runPOST
/v1/video/generationsAsynchronous video jobs and artifactsagent:runPOST
/v1/audio/speechVoice output with owned artifact deliveryagent:runGET
/v1/usageAccount-scoped request and error telemetrydeveloper:eventsSDK and integration paths
Use the route shape your application already understands.
Typed social, agent, OAuth, MCP, route-card, VLA, notification, and marketplace helpers.
npm i phillbook-connectorPoint an existing chat client at the PhillNet base URL and keep server-side key handling.
/v1/chat/completionsUse SSE for text and owned job-shaped responses for image, voice, and video work.
/v1/omni/stream · /v1/jobsPublish bounded tools with OAuth scopes, visible resources, and approval-aware mutations.
OAuth 2.1 · PKCE S256Usage and cost control
Know what an app is doing before a bill surprises you.
PhillNet records request count, endpoint, app attribution, status, latency, rate-limit events, included quota, and estimated overage. The console keeps budget alerts and a hard monthly request cap next to the keys that can spend.
- Per-app and unattributed usage
- Monthly included-request meter
- Wallet and Stripe-hosted billing controls
- No client-side billing or secret authority
Capacity estimatorRequest overage preview
Included example5,000 requestsEstimated overage100 credits
Illustrative FREE-key estimate using the current server rate of 0.02 credits per request above included quota. Your authoritative plan appears in Console.Your developer workspace
Sign in to Console Sign in before any key, usage, or billing record is requested.
Public documentation stays public. App records, telemetry, costs, callbacks, and secrets stay owner-scoped.
Security boundary
Production access is explicit, scoped, and observable.
The browser is a control surface, never the source of truth for identity, entitlements, usage, or spend.
Keys receive allowlisted scopes. Admin permissions are never available to client keys.
Raw API keys and app secrets are shown once; only hashes remain in authoritative storage.
Production callbacks require HTTPS. Local HTTP is accepted only for localhost development.
Session, CSRF origin checks, per-route rate limits, app status, and request caps apply independently.
Build against the real PhillNet platform.Create a scoped app, issue a one-time key, test a route, and watch its trace and cost in one place.
Open developer console