# STORI AI Inc.

> STORI AI is a San Francisco-based AI content-marketing platform that helps brands define their
> identity — archetype, tone, tagline, and colors — and turn that identity into on-brand social posts,
> graphics, images, videos, and go-to-market marketing materials. The product generates personalized
> branded content, schedules and publishes it across digital platforms, and offers analytics, content
> storage, and multi-brand, multi-language, team-collaboration tiers. STORI AI is a web SaaS
> application for marketers and brand teams.
>
> NOTE FOR AGENTS: as of 2026-08-13 STORI AI publishes NO public developer API, no OpenAPI or other
> machine-readable contract, no SDKs on any public package registry, no MCP server, and no A2A agent
> card. There is no programmatic surface to call. This file is a catalog profile generated by API
> Evangelist, not a provider-published document.

## Company

- [Website](https://storiai.com): Product site and sign-up.
- [Pricing](https://www.storiai.com/pricing): Subscription tiers.
- [Blog](https://www.storiai.com/blog): Company and product writing.
- [Roadmap](https://www.storiai.com/roadmap): Published product roadmap.
- [Contact / support](https://www.storiai.com/contact): Support channel.
- [Log in](https://www.storiai.com/login): Application sign-in.
- [Terms of service](https://www.storiai.com/terms)
- [Privacy policy](https://www.storiai.com/privacy)

## APIs

None published. No developer portal, API reference, OpenAPI/AsyncAPI/GraphQL contract, or API base
URL could be found on any host the company controls.

## Artifacts in this profile

- [Domain security probe](security/stori-ai-inc-domain-security.yml): TLS/HSTS/DNSSEC/CAA/SPF/DMARC
  posture for storiai.com.
- [Well-known probe](well-known/stori-ai-inc-well-known.yml): Recorded absence — every
  `/.well-known/` discovery path returns 404.

## Provenance

- generated: 2026-08-13
- method: generated
- source: apis.yml + artifacts in this repository; live probes of storiai.com
- Discovery caveat: every HTML route on www.storiai.com answered HTTP 403 with a Cloudflare
  interstitial ("Just a moment...") during this pass, so the product and pricing pages could not be
  read. Machine-readable paths (`/llms.txt`, `/.well-known/*`) passed through the edge and returned
  genuine 404s.