No authentication
The public resources on this page are intentionally readable without tokens or accounts.
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.
The public resources on this page are intentionally readable without tokens or accounts.
These endpoints describe public studio state. They do not accept mutations or expose internal systems.
Where practical, endpoint data is generated from the same structured records used to render PNS pages.
Static responses are safe to cache. Do not assume every endpoint changes on every deploy.
If a structured endpoint exists, prefer it over trying to reverse-engineer the rendered HTML.
/studio.jsonStudio identity, disciplines, projects, labs and update metadata.
Open →/projects.jsonCurrent public project index.
Open →/roadmap.jsonDirectional Now, Next and Exploring roadmap items.
Open →/updates.jsonStudio update metadata.
Open →/capabilities.jsonDisciplines, capability areas and collaboration routes.
Open →/ecosystem.jsonPublic graph of divisions, projects and relationships.
Open →/faq.jsonCommon studio questions and answers.
Open →/factsheet.jsonConcise studio facts, contact and project references.
Open →/brand.jsonOfficial colors, assets and press-kit references.
Open →/brand.cssReusable CSS custom properties for PNS identity.
Open →/feed.jsonStudio updates in JSON Feed 1.1 format.
Open →/rss.xmlStudio updates in RSS 2.0 format.
Open →/sitemap.xmlGenerated public page index.
Open →/opensearch.xmlBrowser search-provider discovery.
Open →/llms.txtConcise automated-system reference.
Open →Plain HTTP GET requests are enough.
curl https://www.pixelnebulastudios.com/projects.jsonconst projects = await fetch(
'https://www.pixelnebulastudios.com/projects.json'
).then(r => r.json());@import url('https://www.pixelnebulastudios.com/brand.css');
.button {
color: var(--pns-nebula-cyan);
}curl https://www.pixelnebulastudios.com/feed.jsonExisting 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.