# Soldsie

**Canonical:** https://apis.io/providers/soldsie/  
**Website:** https://www.soldsie.com  
**APIs profiled:** 0

Soldsie was a social-commerce platform founded in 2012 in San Francisco by Chris Bennett and Arrel Gray that let retailers sell directly through social media: customers bought products by commenting "Sold" on a merchant's Facebook or Instagram post, while a backend dashboard handled invoicing, customer tracking, and waitlists. Backed by 500 Startups (now 500 Global) and e.ventures, it raised roughly $1M in seed funding and a $4M Series A (2014), and had processed over $25M in transactions across more than 1,000 merchants. The product is now defunct: the soldsie.com apex no longer resolves and www.soldsie.com returns a broken redirect, so there is no live developer portal, API, or documentation surface to enrich.

## Kin Score — 5.0 / 100 (minimal)

Scored 2026-08-21 under rubric 0.12.0. Trend: flat (+0.0 from 5.0).

| Facet | Score |
|---|---|
| Discoverability | 50.0 |
| Contract Quality | 0.0 |
| Governance | 0.0 |
| Contract Governance | 0.0 |
| Operational Transparency | 0.0 |
| Developer Ergonomics | 0.0 |
| Commercial Clarity | 0.0 |
| Access Clarity | 0.0 |

## Agent readiness — 0.0 (human-only)

| Dimension | Value |
|---|---|
| Spec Presence | no |
| Agentic Access | no |
| Reversibility Documented | no |
| MCP Server | no |
| Auth Clarity | no |
| Idempotency | no |
| Error Semantics | no |
| OpenAPI Examples | no |
| Rate Limit Signal | no |
| Event Surface Described | no |
| Agent Skills | no |
| Well Known Catalog | no |
| Consent Identity | no |
| Agent Card | no |
| Dry Run Mode | no |

## Access

Requires approval — onboarding: approval, pricing: unknown, trial: no (confidence: medium).

## Security (1)

- **Soldsie Domain Security** — TLSv1.3 · DMARC

## Tags

Company, Social Commerce, E-Commerce, Comment Selling, Retail, Facebook, Instagram, Defunct

---

Profiled by [API Evangelist](https://apievangelist.com) and published on [APIs.io](https://apis.io/providers/soldsie/). Scores are computed from the provider's own public artifacts under a published rubric.
