Paperless Post

Paperless Post is a New York City based digital and print stationery company whose platform lets people design, send, and manage online invitations, greeting cards, save-the-dates, and free Flyers for weddings, birthdays, holidays, business events, and other occasions. Founded in 2008 by siblings James and Alexa Hirschfeld, it pairs an in-house design studio with licensed designer collections (Oscar de la Renta, Rifle Paper Co., Marimekko and others) and adds RSVP tracking, guest messaging, event websites, mobile apps, and a Party Shop. Paperless Post publishes no public developer program, API reference, or machine-readable specification; the /api/v1 endpoints named in its robots.txt serve its own first-party web and mobile clients only.

Paperless Post is listed with 1 API on the APIs.io network. Tagged areas include Company, Invitations, Event, Greeting Cards, and Stationery.

Paperless Post’s developer surface includes pricing, signup flow, support, engineering blog, authentication, and 17 more developer resources.

29.9/100 thin ▬ flat Agent 17/100 agent aware Front door AI 1/6 silent Heartbeat 50/100 alive saas Full breakdown ↓
scored 2026-11-06 · rubric v0.27.0 · Show this score on your site →
1 API 1 MCP Servers
CompanyInvitationsEventGreeting CardsStationeryConsumerE-CommerceRSVPDesign

Kin Score

Kin Score Kin Score How this is scored →
scored 2026-11-06 · rubric v0.27.0
Regulatory Posture applies to this provider. Its tags matched the Payments regime, so Regulatory Posture carries 15 points of the composite. If this regime is wrong for your business, say so on your provider repo — the applicability map is public and we will correct it.
Create-or-Update Ergonomics could not be measured. We hold no machine-readable contract for this provider to read, so there is nothing to measure a write surface against. Excluded rather than scored zero: never-measured and measured-empty are different facts. Publishing an OpenAPI is what makes this facet — and several others — scorable at all.
The six quality facets above are damped to 85 points between them, because the conditional facet above carries the other 15. That is why each facet's contribution is shown against a damped maximum: raising a quality facet moves the composite by 85% of its nominal weight, not 100%. The full arithmetic is at apis.io/rating/.
Show this score on your site. Kin Score badge preview for Paperless Post It updates itself when the score changes. Paste this where you link to your API docs:
<a href="https://apis.io/providers/paperless-post/"><img src="https://apis.io/badge/paperless-post/card.svg" alt="Paperless Post on APIs.io — Kin Score by API Evangelist"></a>
Other styles, a README pill and a shields.io endpoint are on the badge page.
Raise your score.
Agent readiness — checks not met, largest first (exact, from this profile):
  • Machine-Readable Contract +18 pts — api_specs includes an OpenAPI document
  • Agentic Access Contract +10 pts — agentic_access artifact present (x-agentic-access), graded by author
  • Idempotency +9 pts — OpenAPI mutating operations declare an idempotency key — a header, a request-body property, or a named de-duplication token whose own description says so (verified); else common[].type matches /idempoten/i (documented)
  • Stable Error Semantics +8 pts — OpenAPI $refs a shared error schema across 4xx/5xx responses (verified), else common[].type includes ErrorCatalog / ErrorCodes / DeclineCodes
  • A2A Agent Card +8 pts — a2a/-a2a.yml manifest, graded on conformance.grade against A2A 1.0.0
  • Rate-Limit Signaling +7 pts — OpenAPI responses document X-RateLimit-* / RateLimit headers (verified), else a rate_limits artifact or RateLimits link (documented)
8 more unmet checks in the Agent Readiness table above.
Kin Score — facets with the most composite points still available (weight × headroom):
Each check links to what satisfies it. Publish the artifact, or tell us where it already lives, and the score moves on the next scoring run.
Improve this rating by publishing the missing artifacts — every area above can be raised, and the full rubric is at apis.io/rating/. Every facet and dimension name above is a link: it opens that measurement's own page — what it means, the exact checks that feed it, how the whole catalog distributes on it, and the providers at the top of it. This rating is computed from the provider profile at artifacts.apis.io/paperless-post/apis.yml: open an issue on github.com/api-evangelist/paperless-post to ask a question or point us at an artifact you publish. Submit an artifact on GitHub — free → Manage your own listing — the Influence plan, $499/mo →

Standards implemented 2

Standards this provider implements or carries. De facto ones are profiled and measured by the API Commons; formal ones come from the standards directory and are linked by the provider's own tags. The evidence column says how each claim was established — not that it was made.

measured — observed by APIs.io (platform)
measured — observed by APIs.io (verified)

APIs 1

Individual APIs this provider publishes, each with its own machine-readable definition.

Paperless Post Party Shop Agent Commerce Surface

The Paperless Post Party Shop storefront is the only machine-callable surface on any paperlesspost.com host. It is Shopify-hosted and implements the Universal Commerce Protocol ...

MCP Servers 1

Model Context Protocol servers that expose these APIs to AI agents.

Paperless Post MCP Server

Remote MCP server at partyshop.paperlesspost.com over HTTP; 5 tools listed.

MCP SERVER

Security Posture 2

Authentication, domain security, vulnerability disclosure, and trust-center signals.

Paperless Post Authentication

oauth2/openIdConnect · 2 schemes

SECURITY

Paperless Post Domain Security

TLSv1.3 · HSTS · DMARC

SECURITY

Scopes 1

OAuth scopes governing access to this provider's APIs.

Paperless Post Scopes

4 scopes · authorizationCode

4 scopes

SCOPES

Resources

Get Started 2

Portal, sign-up, and the first successful call

Agent Surfaces 3

MCP servers, agent skills, and machine-readable catalogs

Design & Contract 3

Pagination, idempotency, versioning, errors, and events

Build 1

SDKs, sample code, and the tooling you integrate with

Access & Security 3

Authentication, authorization, and security posture

Operate 2

Status, limits, changes, and where to get help

Commercial 3

Pricing, plans, and the legal terms of use

Company 4

The organization behind the API

Other 1

Properties that don't map to a standard resource type

Source (apis.yml)

apis.yml Raw ↑
aid: paperless-post
name: Paperless Post
description: Paperless Post is a New York City based digital and print stationery company whose platform lets people design,
  send, and manage online invitations, greeting cards, save-the-dates, and free Flyers for weddings, birthdays, holidays,
  business events, and other occasions. Founded in 2008 by siblings James and Alexa Hirschfeld, it pairs an in-house design
  studio with licensed designer collections (Oscar de la Renta, Rifle Paper Co., Marimekko and others) and adds RSVP tracking,
  guest messaging, event websites, mobile apps, and a Party Shop. Paperless Post publishes no public developer program, API
  reference, or machine-readable specification; the /api/v1 endpoints named in its robots.txt serve its own first-party web
  and mobile clients only.
deliveryModel:
  model: saas
  open_source: false
  commercial: true
  callable_host: false
  label: Hosted service · you call their endpoint
  confidence: medium
  source:
  - pricing
  generated: '2026-08-28'
  method: derived
accessModel:
  pricing: unknown
  onboarding: unknown
  trial: false
  try_now: false
  public: false
  label: Unknown
  confidence: low
  probe_state: covered
  source:
  - authentication
  - scopes
  - security
  generated: '2026-11-06'
  method: derived
image: https://avatars.githubusercontent.com/u/282691?v=4
url: https://raw.githubusercontent.com/api-evangelist/paperless-post/refs/heads/main/apis.yml
x-type: company
x-source: harvest:secondary-market
x-tier: stub
x-tier-reason: harvest
specificationVersion: '0.23'
created: '2026-08-04'
modified: '2026-08-04'
tags:
- Company
- Invitations
- Event
- Greeting Cards
- Stationery
- Consumer
- E-Commerce
- RSVP
- Design
tags_raw:
- Company
- Invitations
- Events
- Greeting Cards
- Stationery
- Consumer
- E-Commerce
- RSVP
- Design
apis:
- aid: paperless-post:party-shop
  name: Paperless Post Party Shop Agent Commerce Surface
  description: 'The Paperless Post Party Shop storefront is the only machine-callable surface on any paperlesspost.com host.
    It is Shopify-hosted and implements the Universal Commerce Protocol (UCP) for agent-driven commerce: a UCP merchant profile
    at /.well-known/ucp, an MCP endpoint at /api/ucp/mcp carrying the search_catalog / create_cart / create_checkout / update_checkout
    / complete_checkout tool set, OAuth 2.0 + OpenID Connect customer-account authorization, published agent instructions
    at /llms.txt and /agents.md, and anonymous read-only product and collection JSON endpoints. Checkout completion requires
    contemporaneous buyer approval.'
  humanURL: https://partyshop.paperlesspost.com/agents.md
  baseURL: https://partyshop.paperlesspost.com
  tags:
  - Commerce
  - MCP
  - Agents
  - Storefront
  - Party Supplies
  properties:
  - type: MCPServer
    url: mcp/paperless-post-mcp.yml
  - type: Documentation
    url: https://partyshop.paperlesspost.com/agents.md
  - type: TermsOfService
    url: https://partyshop.paperlesspost.com/policies/terms-of-service
  x-surface: platform-generated
  x-platform: shopify
  x-platform-surface: ucp
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com
- FN: APIs.json
  email: info@apis.io
common:
- type: DomainSecurity
  url: security/paperless-post-domain-security.yml
- type: Website
  url: https://www.paperlesspost.com/
- type: About
  url: https://www.paperlesspost.com/about
- type: Pricing
  url: https://www.paperlesspost.com/pricing
- type: SignUp
  url: https://www.paperlesspost.com/accounts/new
- type: Login
  url: https://www.paperlesspost.com/session/new
- type: TermsOfService
  url: https://www.paperlesspost.com/terms-of-service
- type: PrivacyPolicy
  url: https://www.paperlesspost.com/privacy-policy
- type: Support
  url: https://paperlesspost.zendesk.com/hc/en-us
- type: Blog
  url: https://www.paperlesspost.com/blog/
- type: GitHubOrganization
  url: https://github.com/paperlesspost
- type: Careers
  url: https://www.paperlesspost.com/about/careers
- type: StatusPage
  url: https://status.paperlesspost.com/
- type: Lifecycle
  url: lifecycle/paperless-post-lifecycle.yml
- type: LLMsTxt
  url: llms/paperless-post-llms.txt
- type: WellKnown
  url: well-known/paperless-post-well-known.yml
- type: MCPServer
  url: mcp/paperless-post-mcp.yml
- type: Authentication
  url: authentication/paperless-post-authentication.yml
- type: OAuthScopes
  url: scopes/paperless-post-scopes.yml
- type: Conformance
  url: conformance/paperless-post-conformance.yml
- type: Conventions
  url: conventions/paperless-post-conventions.yml
- type: SecondaryMarket
  url: https://forgeglobal.com/paperless-post_stock/
x-coverage:
  state: covered
  reason: agent-commerce-surface-only
  detail: The core Paperless Post invitation product at www.paperlesspost.com has no developer program and no machine-readable
    contract — every OpenAPI, GraphQL, agent-card and /.well-known probe 404s — but the Party Shop storefront at partyshop.paperlesspost.com
    serves a full UCP/MCP agent-commerce surface (llms.txt, agents.md, /.well-known/ucp, OAuth/OIDC discovery), so the provider
    is covered on that surface rather than empty.
  evidence:
  - url: https://partyshop.paperlesspost.com/.well-known/ucp
    status: 200
  - url: https://partyshop.paperlesspost.com/llms.txt
    status: 200
  - url: https://www.paperlesspost.com/openapi.json
    status: 404
  - url: https://www.paperlesspost.com/.well-known/agent-card.json
    status: 404
  checked: '2026-08-04'
x-enrichment:
  date: '2026-08-04'
  status: enriched
  artifacts_added: 15
  pass: local-v1

Paperless Post API — frequently asked questions

Does Paperless Post have an API?

Yes. APIs.io lists 1 API from Paperless Post, including Paperless Post Party Shop Agent Commerce Surface.

How do I authenticate with the Paperless Post API?

Paperless Post documents its authentication (oauth2/openIdConnect · 2 schemes). The details are profiled on APIs.io as Paperless Post Authentication.

Does Paperless Post have an MCP server?

Yes. APIs.io lists 1 MCP server for Paperless Post: Remote MCP server at partyshop.paperlesspost.com over HTTP; 5 tools listed.

Is the Paperless Post API ready for AI agents?

Paperless Post has a Kin Score of 29.9 out of 100 (thin) and an Agent Readiness score of 17.4 (agent-aware), scored by API Evangelist on 2026-11-06.

Work with this as data

Every provider here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for providers

9 MCP tools reach this
  • find_providersBrowse and filter every provider in the catalog.
  • get_provider_artifactsEvery artifact this provider publishes, grouped by type.
  • get_provider_operationsEvery operation across all of their OpenAPIs — one call instead of parsing every spec.
  • get_provider_toolsEvery MCP tool they ship, with the operation each wraps.
  • get_provider_evidenceHow each part of their score was established. Free — the basis for a claim should not sit behind it.
  • get_provider_ratingPRO — composite, band, trend and facet scores.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This provider
curl "https://apis.io/api/v1/providers/paperless-post"
All providers
curl "https://apis.io/api/v1/providers?limit=25"
Every operation they expose
curl "https://apis.io/api/v1/providers/paperless-post/operations?limit=25"
How their score was established
curl "https://apis.io/api/v1/providers/paperless-post/evidence"

Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

A second provider on the same verified email joins the account you already have.