POST /v1/caption-pack

Captions on demand. Built for developers and AI agents.

POST a topic, audience, and tone. Get back platform-ready social captions with hashtags as clean JSON — in under 100 milliseconds.

Get API access — $10 for 500 calls
No subscription Credits never expire 2¢ per call
request → response
POST /v1/caption-pack
// request
{
  "topic": "patching & update habits",
  "audience": "IT professionals",
  "tone": "confident",
  "platform": "linkedin",
  "count": 3
}
// response · 200 OK · 1 credit
{
  "captions": [
    { "hook": "…", "body": "…", "cta": "…" }
  ],
  "hashtags": ["#CyberSecurity", "#ITLife"],
  "credits_remaining": 499
}

free_tier

Try it free — 25 calls, no card.

Free keys are the exception: 25 calls, 7 days, then they're gone.

The Caption-Pack API now has a free tier. Mint a 25-call free key — no credit card, no catch. Or skip the key entirely and hit the playground for a keyless try. Free keys are abuse-guarded (one free key per IP per day, 7-day expiry) and can never be converted to paid. Ready for more? $10 gets you 500 calls via Stripe.

Your key appears once — save it somewhere safe right away. Then use it as your API key and make your first call; the example above is copy-paste ready. Free keys hold 25 calls and expire after 7 days.

The playground is a keyless POST endpoint — details in the API spec.

example_outputs

Examples

Real outputs from the API — same inputs, same quality, every time.

Instagram

password managers · small business owners · warm

Hook

Found a USB stick in the parking lot? Congratulations, it's a trap. 💽

Body

Dropped drives are one of the oldest tricks in the book — curiosity does the attacker's work for them. Found media goes to security, never into your laptop.

CTA

Would you plug in a USB you found on the ground? (Say no. 😅)

Hashtags

#CyberSecurity #InfoSec #TechTips — 324 chars

X

morning routines · busy professionals · bold

Hook

The morning routines mistake almost everyone makes.

Body

After years of watching people tackle morning routines, the pattern is clear: the ones who win aren't the most talented — they're the most consistent.

CTA

Stop scrolling, start doing. Your first morning routines move happens in the next 10 minutes. 👇

Hashtags

#MorningRoutines #Morning #Routines — 280 chars

LinkedIn

remote work · engineering managers · professional

Hook

Remote work isn't complicated. It's just poorly explained.

Body

Here's the short version: start small, stay consistent, and ignore the gurus selling shortcuts. Engineering managers get the best results from fundamentals done well — not hacks.

CTA

What's one remote work lesson you'd pass to someone starting out?

Hashtags

#RemoteWork #Remote #Work #Tips #HowTo — 345 chars

TikTok

study hacks · college students · bold

Hook

Stop doing study hacks the hard way.

Body

You don't need another course on study hacks. You need a simple checklist and the discipline to run it. Start today, thank yourself in 90 days.

CTA

Stop scrolling, start doing. Your first study hacks move happens in the next 10 minutes. 👇

Hashtags

#StudyHacks #Study #Hacks #Tips #HowTo — 313 chars

how_it_works

Three steps. No subscription.

Prepaid credits, one endpoint, JSON in and out. Everything you need to go from brief to posted copy.

1

Grab a key

Pay $10, get an API key with 500 prepaid credits. No subscription, no surprise bills.

2

POST your brief

Send topic, audience, tone, and platform to /v1/caption-pack. One call = one credit.

3

Ship the copy

Every call returns hooks, bodies, CTAs, and hashtags — plus credits_remaining so you always know where you stand.

why_prepaid_credits

Why prepaid credits

You pay once, up front, and the meter only moves when you call. Built for predictable budgets and autonomous agents alike.

Predictable

$10 buys 500 calls — 2¢ each. The meter never runs without you.

Fast

Deterministic template engine seeded from proven, human-approved caption packs. No LLM latency, no per-call AI bill passed to you.

Agent-native

Key auth, JSON in / JSON out, rate limits you can build around.

pricing

Two packs. One simple model.

No seat math, no renewal ambush. Buy the prepaid pack that fits, then top up whenever you need it.

STARTER PACK

$10 for 500 calls

2¢ per call

The easy yes for trying paid.

  • 500 prepaid credits — 1 credit per call
  • Request 1–10 captions per call, same price
  • Paid credits never expire
  • API key issued on payment, crediting is automatic
  • Failed calls never cost credits
Choose Starter — $10

Secure checkout via Stripe. All sales final.

How metering works. One credit per call, regardless of how many captions you request (1–10).

Out of credits? The API returns a clean 402 with a top-up link. Choose your pack, keep going — crediting is automatic.

HTTP 402 Payment Required { "error": "insufficient_credits", "credits_remaining": 0, "top_up_url": "…" }

faq

Questions, answered

The short version of everything buyers ask before their first call.

What platforms are supported?+

Instagram, LinkedIn, X, and TikTok — each with its own char limits and hashtag rules baked in.

Can I use this in my AI agent?+

That's exactly who it's for. Key auth, deterministic output, predictable cost.

What happens when I run out of credits?+

You get a clean 402 response with a top-up link. Pay $10, keep going — crediting is automatic.

Do unused credits expire?+

No. They're yours until you spend them.

Refunds?+

All sales are final — no returns or refunds. Credits never expire, so they're yours until you spend them. See the Terms of Service for the full policy.

terms_of_service

Terms of Service

The full agreement, in plain language. Buying credits or using the API means you agree to these terms.

Operator: Jeshua Domingo, Torrance, CA. By buying credits or using the API you agree to these terms.

01 What you're buying

Prepaid API credits, not a subscription. 1 credit = 1 successful call to /v1/caption-pack. Failed calls never cost credits. $10 for 500 credits. Credits never expire, are tied to your API key, non-transferable, no cash value.

02 Payments and fees

Processed by Stripe; we never see or store card numbers. Prices can change only for future purchases — credits already bought keep working as sold, no retroactive repricing. Failed payments mean credits aren't issued. Taxes are the buyer's responsibility.

03 Refunds

All sales are final, no returns or refunds. If payment is taken but credits are never issued, that's our mistake to fix — contact support.

04 Chargebacks and disputes

Before filing a chargeback or payment dispute, you agree to email support and give us 7 days to make it right. The 7-day period starts only when we receive a complete support ticket: it must include the Stripe charge ID (or receipt number) from your payment confirmation and a clear description of the issue. If you file without contacting us first and the dispute is decided in our favor, you reimburse the dispute fee. Repeated chargebacks after receiving service = fraud: key revoked, credits forfeited. Unresolved disputes go to small-claims court or binding arbitration in Los Angeles County, California; no class actions; California law governs.

05 Acceptable use

No spam, deception, harassment, or unlawful content. Abuse may lead to rate-limiting, suspension, or revocation.

06 Liability

Service provided as-is, no uptime guarantee. Total liability capped at what you paid in the 12 months before the claim. We are never liable for indirect, incidental, or consequential damages (lost profits, lost data, etc.), even if we were advised of the possibility of such damages. You indemnify us for your use of the API output.

07 Your content, our tech

Generated captions are yours to use, including commercially. The API, template engine, and caption corpus stay ours.

08 Privacy

Caption-Pack collects only what's needed — API usage logs for metering and abuse prevention. Payment records are processed by Stripe. We do not collect or store email addresses, and no email is required for free-trial keys. For paid purchases, Stripe collects the email you provide at checkout for payment receipts; Stripe handles it under its privacy policy, and Caption-Pack does not store it. We don't sell data.

09 Changes

Terms may be updated with 14 days' notice; continued use means acceptance.

Service Level Agreement

1. Availability

We target 99% monthly availability across all Caption-Pack API endpoints, excluding scheduled maintenance.

If availability falls below 99% in any calendar month, paid customers automatically receive a 10% extension in API call credits.

2. Support

  • Email: xena.domingo.ea@gmail.com
  • Response time: within 2 business days.
  • Critical outages (API fully unreachable): same-day acknowledgment.

3. Scheduled maintenance

Announced at least 48 hours in advance. Scheduled maintenance does not count against availability.

4. Exclusions

This SLA does not cover downtime caused by: our hosting provider's platform issues, scheduled maintenance, misuse of the API, or events beyond our reasonable control.

5. Upgrade path

This SLA reflects our current entry-level hosting. When Caption-Pack migrates to dedicated hosting, this document will be replaced with a guaranteed 99.9% uptime SLA.

Security Review

1. Data minimization

We store the minimum needed to operate the service:

  • Stored: API key hashes (never raw keys), credit balances, timestamps, endpoint called, IP address, user agent.
  • Not stored: request content — your topics, audiences, and tones are never written to disk. We record that a call happened, never what it contained.
  • Not collected: emails, names, or any customer profile data. No account required.
  • Playground: IP + user agent + timestamp only.

2. Key handling

  • Keys are stored as hashes and transmitted as bearer tokens over HTTPS.
  • Revocation is supported and checked on every call.
  • Free-trial keys: 25 credits, 7-day expiry, never convertible or top-up-able — abuse-resistant by design.
  • Operator endpoints are gated by a token that is not stored in the repository.

3. Payments

  • Checkout is hosted by Stripe — card data never touches our servers.
  • Stripe webhooks are signature-verified and idempotent (duplicate deliveries cannot double-credit).

4. No LLM in the loop

Caption-Pack uses a deterministic template engine. Customer input is never sent to a third-party model and never used for training. There is no model to leak into.

5. Known limitations

  • One-person operation. Incident response is via email with a 2-business-day target (per the SLA).
  • MCP key transport. The Smithery MCP deployment currently passes the API key as a query parameter, which can appear in server access logs. Risk is limited (logs are only visible to the service owner). Header-based authentication is the planned hardening item.
  • Entry-level hosting. The API runs on Render and Turso free tiers; their platform security postures apply.

6. Incident response

  • Contact: xena.domingo.ea@gmail.com
  • Suspected key compromise: the key is revoked and a replacement issued.
  • Payment issues: handled through Stripe's dispute and refund tooling.

privacy_policy

Privacy Policy

We keep data collection narrow and tied to running the service. This policy explains the limited information needed to provide Caption-Pack and how long that information stays with us.

01 What we collect

When you buy credits, Stripe collects your email address so it can send receipts. API keys are stored only as SHA-256 hashes, never as plaintext. We keep API usage logs—including calls, timestamps, and error counts—to meter credits and prevent abuse. IP addresses are used only for rate limiting: the free trial allows one key per IP every 24 hours, and the playground allows five calls per hour per IP.

02 Payments

Stripe processes every payment. We never see or store your card number.

03 What we never do

We do not sell your data. We do not use your prompts, topics, or captions to train any model. Caption-Pack uses deterministic templates; there is no machine-learning model in the loop.

04 Data retention

Free-trial keys and their related logs expire automatically after seven days. Paid keys and credit records remain while you hold credits. Aggregate public statistics—counts only, with no IP addresses or API keys—may be kept indefinitely.

05 Questions about your data

Email xena.domingo.ea@gmail.com.

Last updated: October 3, 2026.

contact

Support

Questions about credits, keys, or a payment that didn't land? Reach out — disputes start here too, per the terms above.

Support Email xena.domingo.ea@gmail.com for help with credits, keys, or payments. Everything you need — pricing, refunds, and dispute handling — is also spelled out in the Terms of Service above.