Production APIs for accessibility testing, deployed-app exposure checks, and agent approval controls. Planned product APIs remain clearly labeled until their authentication, metering, and contracts are ready.
POST /v1/shield/scan
Authorization: Bearer sk_shield_••••
Content-Type: application/json
{ "url": "https://example.com" }
200 OK scan · findings · evidenceFind accessibility problems on your website and verify that they were fixed.
Scan a deployed webpage for automatically detectable accessibility issues, receive prioritized remediation guidance, and rescan to confirm changes.Check whether your live application is exposing data or secrets it should not.
Run read-only checks for anonymous Supabase access signals, missing RLS signals and secrets bundled into browser JavaScript.Require approval before an AI agent performs a risky action.
Record proposed agent actions, apply configurable risk thresholds, approve or reject held actions, and retain an independent outcome record.These prices are the intended beta plans, not charges being collected today. Access opens only after authentication, tenant isolation, metering and product-specific terms pass review.
Answer, qualify and route calls inside your own customer experience.
Planned surface: call events, structured lead records, routing outcomes and provider webhooks. Voice and SMS charges will be passed through separately.Send a wager and receive a structured, research-backed analysis.
The customer product already runs the analysis engine. Public API access requires separate keys, metering and commercial data-use terms before launch.Add structured intake and self-guided preparation workflows to another product.
Informational preparation only—not legal, financial or licensed-professional advice. Public access will launch with workflow isolation and explicit jurisdiction metadata.Connect operational records and workflows without replacing the customer’s interface.
Planned surface: customers, projects, invoices and workflow events. Write access will use narrow scopes and Ledger-compatible approval gates.Want beta access? Email jathan@3stoneai.com with the API, use case and expected monthly volume.
Choose a product, create a key through secure Stripe Checkout, store it server-side, and call the production endpoint. Responses are JSON and errors use standard HTTP status codes.
Use Shield for accessibility, Sentinel for deployed-app exposure, or Ledger for agent control.
Keys are delivered once after checkout. Keep them in a server-side secret store.
Import the Postman collection or use the OpenAPI contract from GitHub.
Use evidence and explicit statuses in your own workflow; never infer a guarantee the API does not make.