Platform API
Most of what you need never requires code: you describe an app, PhiCo builds it, and you publish it from your account. This section is for the other case — when something outside PhiWebs has to read from or write to your apps.
Everything here talks to one host:
https://api.phiwebs.comWhat you can do
| You want to… | Start with |
|---|---|
| Read or change your apps and their pages from another system | API reference |
| Generate or revise pages programmatically | AI integration |
| Know what a ceiling looks like before you hit it | Rate limits & quotas |
| Connect a service you already use | Integrations |
| Understand what happens between a sentence and a live page | How it works |
Authentication
Authenticated endpoints take a bearer token. You obtain one from your account, or through the OAuth flow when you are acting on behalf of another World. Which endpoints a token may call depends on the plan the World is on — the rate limits page covers both the ceilings and the shape of the response when you cross one.
Visitors signing in to your app are a different mechanism entirely, with their own identities and their own records. That is covered in Visitor sign-in, not here.
Building your own blocks
The engine that renders an app — its SDK, its CLI and the interfaces for defining blocks and capabilities — is documented separately from the platform, and this site no longer carries it. If you are building at that level, talk to us and we will point you at the right material.