Developers

The public surface has an interface.

PNS publishes structured studio data, feeds, discovery metadata and brand tokens as static public endpoints. No API key is required for these read-only resources.

01

No authentication

The public resources on this page are intentionally readable without tokens or accounts.

02

Read-only

These endpoints describe public studio state. They do not accept mutations or expose internal systems.

03

Same source as the site

Where practical, endpoint data is generated from the same structured records used to render PNS pages.

04

Cache friendly

Static responses are safe to cache. Do not assume every endpoint changes on every deploy.

Examples

Nothing exotic required.

Plain HTTP GET requests are enough.

curl
curl https://www.pixelnebulastudios.com/projects.json
JavaScript
const projects = await fetch(
  'https://www.pixelnebulastudios.com/projects.json'
).then(r => r.json());
Brand CSS
@import url('https://www.pixelnebulastudios.com/brand.css');

.button {
  color: var(--pns-nebula-cyan);
}
Studio updates
curl https://www.pixelnebulastudios.com/feed.json
Stability

Public does not mean frozen forever.

Existing URLs should remain durable. We will prefer additive changes over gratuitous renames.

Fields may expand. Consumers should ignore unknown fields rather than treating them as errors.

Experimental internals stay private. A feature does not become a supported API merely because the studio uses it internally.

Breaking changes should be documented. If a public data shape eventually needs a major redesign, the safer path is a versioned endpoint.