# Pixis

> Pixis is an AI-powered advertising and marketing platform for consumer brands, built on
> proprietary codeless AI infrastructure that plans, creates, and optimizes digital advertising
> across channels. Its products include Prism (conversational performance-marketing agent),
> Adroom (generative AI creative production), Performance AI, Creative AI and Visibility
> (AI-search presence tracking). Pixis connects to Google, Meta, TikTok and Salesforce to
> automate media buying and creative generation. Backed by SoftBank Vision Fund, with
> engineering operations in India.

**This file is generated by API Evangelist, not published by Pixis.** It is written from the
API Evangelist profile at https://github.com/api-evangelist/pixis and from live probes carried
out on 2026-08-12. Pixis serves no llms.txt of its own on any of its hosts.

## Bottom line for an agent

Pixis has **no public developer API**. There is no OpenAPI, no GraphQL schema, no MCP server,
no A2A agent card, no SDK in any package registry, no webhook catalog, no public API reference,
and no public API key issuance. An agent cannot call Pixis programmatically. Pixis is operated
through its web application after a sales conversation.

The one machine-readable contract Pixis does publish is an OpenID Connect discovery document
for **application login**, not for API access.

## What Pixis does publish machine-readably

- [OpenID Connect discovery](https://auth.pixis.ai/.well-known/openid-configuration): OIDC/OAuth 2.0
  metadata for the Pixis login domain (Auth0 custom domain). Issuer `https://auth.pixis.ai/`.
- [OAuth 2.0 authorization server metadata](https://auth.pixis.ai/.well-known/oauth-authorization-server):
  RFC 8414 document, byte-identical to the OIDC discovery response.
- [JSON Web Key Set](https://auth.pixis.ai/.well-known/jwks.json): two RSA (RS256) signing keys.

Authorization code with PKCE (S256) is the flow the Pixis web app uses. `client_credentials`,
device code, token exchange and JWT bearer grants are advertised. The advertised scopes are the
stock OIDC identity claims (`openid`, `profile`, `email`, `offline_access`, and profile claim
scopes) — there are no Pixis resource scopes.

## Human-readable surfaces

- [Website](https://pixis.ai/)
- [Products](https://pixis.ai/products/)
- [Prism product documentation](https://prism-docs.pixis.ai/): 77 pages of end-user guidance —
  onboarding, integrations, agents, campaign portfolio, scheduled workflows, brand knowledge.
  Product documentation, not API documentation.
- [Integrations](https://pixis.ai/products/integrations/): names Google, Meta, Salesforce,
  Advance and Adroom. States "no complicated setup — just connect to your existing marketing
  stack". No API, key, OAuth or webhook detail.
- [Compliance](https://pixis.ai/products/compliance/): claims SOC 2, ISO and GDPR. No report,
  certificate number, auditor, period, or trust portal.
- [Privacy policy](https://pixis.ai/privacy-policy/)
- [Blog](https://pixis.ai/blog/)
- [Contact](https://pixis.ai/contact/) — support@pixis.ai
- [Book a demo](https://pixis.ai/get-a-demo/)

## Pricing

Not published. No pricing page exists across the 547 URLs in the pixis.ai sitemap. Every route
to commercial terms is a demo request form.

## Status

[status.pixis.ai](https://status.pixis.ai/) returns HTTP 200 but is **password protected** —
it renders the literal text "This status page is password protected." No components, uptime
figures or incident history are publicly readable.

## Absences measured on 2026-08-12

- `api.pixis.ai`, `docs.pixis.ai`, `developer.pixis.ai`, `developers.pixis.ai`, `mcp.pixis.ai`:
  DNS records exist behind Cloudflare, but every request returns HTTP 530, Cloudflare error
  code 1016 (Origin DNS Error). No origin is reachable.
- `pixis.stoplight.io`: a Stoplight developer-portal workspace exists (workspace 104607,
  created 2022-08-28) but has **zero public projects**, and its own embedded state reports
  `"locked": true, "lockReason": "overusage"` as of 2026-05-08.
- `github.com/pixisai`: the GitHub organization exists with 0 public repositories.
- No package on npm, PyPI, RubyGems, crates.io, Maven Central, NuGet or pkg.go.dev.
- No public Postman workspace or collection.
- No `/llms.txt`, `/.well-known/security.txt`, `/.well-known/api-catalog`,
  `/.well-known/ai-plugin.json`, `/.well-known/agent-card.json` or `/.well-known/agent.json`
  on any Pixis host. The marketing site and every Firebase-hosted product SPA answer arbitrary
  paths with HTTP 200 and an HTML shell — treat those 200s as misses.

## Live services observed (undocumented, first-party backends)

Recorded for completeness. These are not developer APIs; none is documented and none accepts a
third-party integrator.

- `https://core-performance.pixis.ai/` — Express + express-jwt. Anonymous requests return 401
  `credentials_required`. `GET /health` returns `{"success":true,"message":"Server Running Fine"}`.
- `https://ws.pixis.ai/` — Socket.IO / Engine.IO v4 realtime service. The handshake at
  `/socket.io/?EIO=4&transport=polling` returns 200 with a session id. No channel or event
  catalog is published.

## API Evangelist artifacts in this repo

- `well-known/pixis-well-known.yml` — full /.well-known/ probe across 12 hosts, 60 paths
- `authentication/pixis-authentication.yml` — OIDC/OAuth profile
- `scopes/pixis-scopes.yml` — the 14 advertised OIDC scopes
- `conformance/pixis-conformance.yml` — standards conformance with per-item evidence
- `conventions/pixis-conventions.yml` — observed cross-cutting semantics
- `errors/pixis-problem-types.yml` — the one observable error envelope
- `lifecycle/pixis-lifecycle.yml` — status, versioning, deprecation, developer portal
- `plans/pixis-plans-pricing.yml` — plan_count 0
- `rate-limits/pixis-rate-limits.yml` — limit_count 0
- `security/pixis-domain-security.yml` — TLS/HSTS/SPF/DMARC/DNSSEC/CAA
- `security/pixis-trust-center.yml` — compliance claims and what backs them
- `security/pixis-vulnerability-disclosure.yml` — none published