# Famous / Amaze > Famous (famous.co) returns a 301 to Amaze (amaze.co), the creator-commerce platform operated by > Amaze Holdings, Inc. Amaze runs Amaze Commerce (creator storefronts and AI product creation), > Spring (spri.ng, the creator storefront brand formerly known as Teespring), Amaze Live (shoppable > livestreams) and Amaze Media (performance marketing). It reports 190K+ creators, 1.7B+ lifetime > fan reach and operations in 183 countries. Generated by API Evangelist on 2026-08-13. The provider publishes no llms.txt of its own — /llms.txt returned 404 on amaze.co, amazecommerce.com and spri.ng. This file is GENERATED from the provider's own public artifacts, all of which are linked below. ## The API Amaze's one public, machine-readable API is the **Spring Seller API** — a Swagger 2.0 contract with 24 operations, served live at `https://api.teespring.com/`. It is documented behind a Swagger UI at https://api.teespring.com/docs. It is served on Spring's ORIGINAL teespring.com domain, not on any of the newer brand domains, and its own docs prose still says "Teespring". - [API reference (Swagger UI)](https://api.teespring.com/docs): the only developer documentation that exists. Four authentication steps plus the generated operation list. - [Machine-readable contract](https://api.teespring.com/swagger_doc/): Swagger 2.0, 24 operations, three tags (`seller`, `v1`, `internal`). ### Authentication 1. Obtain an `app_id` from Spring. There is no self-serve key page — a human must request it. 2. `POST /v1/auth-tokens` with form fields `app_id`, `email`, `password` (the seller's Spring login credentials). 3. Read `access_token` from the 201 response. It expires after 24 hours. Requesting another one returns the current token rather than minting a new one. 4. Send `access_token` as a **query parameter** on every seller request. Public storefront reads take `app_id` as a query parameter instead. There is no OAuth 2.0, no OpenID Connect, no scopes, and no `/.well-known/` discovery on any host. ### Operation groups - `seller/v1/*` — the authenticated seller: dashboard, summary (period: today, yesterday, week, month, seven_days, thirty_days), campaigns, campaign roots, orders, payouts, promotions, volume discounts, and buyer messaging. - `v1/*` — public storefront reads: campaigns by slug, categories, recommender collections, rush prices, trending search suggestions, plus the authenticated user profile and saved addresses/cards. - `internal/v1/*` — inbound Stripe dispute webhook receivers. Not developer operations. ### What an agent needs to know before calling - Errors are ad-hoc JSON, not RFC 9457, and the envelope is inconsistent: `{"error": "..."}` on some paths and `{"error": {"message": "..."}}` on others. - An invalid enum value returns **404**, not 400 or 422. - Unknown paths return **301**, not 404. Do not follow redirects; assert `content-type: application/json` before parsing. - No rate-limit headers are returned and no limits are published. - No idempotency key is supported. `POST /seller/v1/messages/send` emails real buyers, so a retry after a timeout can double-send. Treat it as human-in-the-loop. - `x-request-id` and `x-correlation-id` are returned on every response and are useful for support, though nothing documents them. - Credentials travel in the URL query string, so they land in logs and Referer headers. ## Other machine-readable contracts Amaze publishes proto3 gRPC service definitions to npm under the `@teespring` scope. These describe INTERNAL services with no published endpoint — they are contracts, not a callable API. - [@teespring/subscriptionscoordinator-proto](https://www.npmjs.com/package/@teespring/subscriptionscoordinator-proto) 1.2.7 (2025-01-13): subscriptions, Stripe, Stripe webhooks, DNS, Netlify, OpenSRS. - [@teespring/user-identity-service-proto](https://www.npmjs.com/package/@teespring/user-identity-service-proto) 0.8.0 (2023-08-09): identity, onboarding slides, persona survey. - [@teespring/onboarding-proto](https://www.npmjs.com/package/@teespring/onboarding-proto) 1.1.0 (2023-06-16): task lists and task-list status. ## Client libraries None. Amaze publishes no client SDK for the Spring Seller API in any language. The only npm package named `teespring` is a third-party, unmaintained 2016 wrapper for a private API — not an Amaze artifact. ## Security - [Vulnerability disclosure](https://spri.ng/about/security): report to security.team@spri.ng. No bug bounty, no `/.well-known/security.txt`, no published certifications and no trust center. ## Products and pricing - [Amaze Commerce](https://amazecommerce.com/) — creator storefronts and AI product creation. - [Amaze Commerce pricing](https://amazecommerce.com/pricing) — Free $0/mo (1 GB storage), Basic $9.99/mo (5 GB, 2x usage), Pro $19.99/mo (20 GB, 4x usage, "Coming Soon"). These are platform subscriptions; no price is attached to API access. - [Spring](https://spri.ng/) — the creator storefront brand, formerly Teespring. - [Amaze Live](https://amazelive.com/) — shoppable livestreams. - [Sign up](https://app.amazecommerce.com/signup) / [Log in](https://teespring.com/login) ## Company - [Amaze](https://amaze.co/) / [About](https://amaze.co/about-us) - [Blog](https://blog.amaze.co/) - [Help center](https://kb.spri.ng/) — creator and fan support only; no developer section. - [GitHub](https://github.com/teespring) — organisation name "Spring", 24 public repositories, mostly Ruby infrastructure forks. - [Investor relations](https://ir.amaze.co/) — Amaze Holdings, Inc. is publicly traded. - [Careers](https://jobs.lever.co/amaze) - [Terms of service](https://www.amaze.co/policies/commerce/terms-of-service) / [Privacy policy](https://www.amaze.co/policies/corporate/privacy-policy) ## Not published No MCP server. No A2A agent card. No outbound webhooks or AsyncAPI. No status page (status.spri.ng and status.teespring.com are both NXDOMAIN). No changelog. No CLI. No sandbox or test mode. No deprecation or versioning policy. No `/.well-known/` documents on any host.