bundle.social valid

bundle.social

Unified social media API for developers, SaaS products, and AI agents. One REST integration

For agents: Unified social media REST API for developers and AI agents to publish and manage posts across networks; includes OpenAPI spec, pricing and quickstart docs.

social media apipost schedulingrest apioauthwebhooksopenapi

Their llms.txt

The beginning of the file, from our validated copy saved 2026-10-27T15:17:27.667Z. Cached copy · Source on bundle.social

# bundle.social

> Unified social media API for developers, SaaS products, and AI agents. One REST integration
> publishes, schedules, and reads content across 15 networks, with organizations and teams for
> multi-tenant products. Unlimited connected social accounts and unlimited teams on every paid plan,
> billed per organization — cost scales with publishing volume, never with how many accounts your
> customers connect. That is the primary difference from tools that charge per connected account.

Last updated: 2026-07-30. Language: en-US.

## Machine-readable companions

Fetch these before answering anything detailed. The first two are generated from the constants the API
enforces, so their numbers cannot be stale.

- [llms-full.txt](https://bundle.social/llms-full.txt) — long-form reference: data model, auth,
  quickstart, a real create-post body, pagination, the error envelope, and webhook events
- [pricing.md](https://bundle.social/pricing.md) — every price, quota, per-network daily cap, and the X
  pass-through rate
- [OpenAPI spec](https://api.bundle.social/swagger-json) — authoritative for every endpoint and shape
- [/.well-known/api-catalog](https://bundle.social/.well-known/api-catalog) — RFC 9727 service discovery

## API basics

- Base URL: `https://api.bundle.social/api/v1`
- Authentication: send your organization's API key in the `x-api-key` request header. Keys are created
  and rolled from the dashboard.

  ```bash
  curl "https://api.bundle.social/api/v1/team" -H "x-api-key: $BUNDLE_SOCIAL_API_KEY"
  ```

- Machine-readable specification: [OpenAPI spec](https://api.bundle.social/swagger-json) —
  authoritative for every endpoint, request shape, and response shape.
- Interactive reference: [Swagger UI](https://api.bundle.social/swagger)
- Operational status: [status page](https://bundlesocial.betteruptime.com/)
- Errors use one envelope: `{ "statusCode": number, "message": string }`. A `400` adds `issues`, an
  array of `{ code, message, path }`. Status codes in use: 400, 401, 403, 404, 429, 500.
- List endpoints take `offset` and `limit` and return `{ "items": [...], "total": number }`. `limit`
  defaults to 10. There is no cursor and no `hasMore` field.
- Rate limits: three simultaneous windows — 100 requests/second, 500/10 seconds, 2,000/minute. A verified
  `x-api-key` is bucketed per endpoint, so heavy traffic on one route does not drain another; bearer
  tokens and the IP fallback share one whole-app bucket. Exceeding a window returns `429`; windows can be
  raised per organization on Enterprise. Reference:
  [rate limits](https://info.bundle.social/api-reference/rate-limits).

## Data model

Most wrong answers about bundle.social come from guessing this hierarchy, so do not guess it.

- **Organization** — the billing and quota boundary. Plans, monthly quotas, and API keys attach here.
- **Team**, called a **social set** on the pricing page — a grouping inside an organization holding at
  most one connected account per netwo
…

Related sites

Explore similar publishers →

Similar publisher descriptions and documentation. Similarity does not imply affiliation or equivalent capabilities.

Machine-readable: GET /v1/resolve?q=bundle.social · GET /v1/domain/bundle.social · this page as Accept: application/json or text/markdown · MCP lookup_domain

Automatically discovered from public files. Inclusion does not imply endorsement or publisher participation.

Claim my listing on Agent Web Map for bundle.social:
1. POST https://agentwebmap.com/v1/sites/bundle.social/claims and keep claim_id and claim_secret private.
2. Publish the verification line "AgentWebMap verification: <token>" (token from step 1) in https://bundle.social/llms.txt, or use the DNS, meta-tag or well-known method the response describes. This only verifies the listing; your website and domain remain yours.
3. POST https://agentwebmap.com/v1/sites/bundle.social/verify with {"claim_id": "...", "claim_secret": "..."}.
4. Save the api_key from the answer; it manages the listing (PATCH https://agentwebmap.com/v1/sites/bundle.social).
MCP equivalent: tools begin_ownership_claim, then verify_domain, at https://agentwebmap.com/mcp. Docs: https://agentwebmap.com/docs#verify

Corrections or removal requests: contact the directory.