start

From zero to a verdict in three commands

There is no password, no sales call, and no going-live step. The key you get in command one is your production key — it starts working the moment credit lands in command two, and a cent buys a page.

1 · Sign up, get your key

sign up
curl -X POST https://api.hiddencontent.ai/v1/signup \
-H 'content-type: application/json' \
-d '{"email": "[email protected]", "name": "Your Company",
"acceptTerms": "I am acquiring this service for business use and agree to the Terms of Service at https://hiddencontent.ai/terms"}'
# → { "customerId": "cus_…", "token": "hcs_live_…", "livemode": true, … }
# Store the token now — only its hash is kept, so it is shown exactly once.

Prefer GitHub? POST /v1/signup/github runs a device flow and lands on the same kind of account — and signing in again later recovers it. Details in theAPI documentation.

2 · Buy credit

buy credit
curl -X POST https://api.hiddencontent.ai/v1/billing/checkout \
-H "authorization: Bearer $HCS_KEY" \
-H 'content-type: application/json' \
-d '{"amountCents": 1000}'
# → { "url": "https://checkout.stripe.com/…", "pages": 1000, … }
# Open the url, pay $10, and 1,000 pages land on your balance.

Minimum $10, maximum $5,000 per purchase. Purchased credit never expires, and unused balance is refundable on request. Card details go to Stripe's hosted page — they never touch this API.

3 · Analyze

analyze
curl -X POST https://api.hiddencontent.ai/v1/analyze \
-H "authorization: Bearer $HCS_KEY" \
# → { "verdict": "clean", "findings": [], "certificate": { … }, … }
# …or, when something is hidden in the file:
# → { "verdict": "suspicious",
# "findings": [{ "technique": "docx.vanish", "excerpt": "…", … }], … }

Seven formats, one endpoint — see a real analysis end to end, certificate included, before you run your own.GET /v1/usage shows your balance;402 tells you the exact shortfall before anything is charged. Optional: auto-refill — below X pages, charge $Y — is one consented call away, and one call to turn off. See the docs.

Not ready to integrate?

Leave your email and a line — a human reads these and replies. Or write to[email protected] directly.