Getting started -- Verify API
The shortest path from zero to a working, authenticated Verify API request.
1. Obtain a token
Verify's audit/readiness endpoints and Sentinel Watch are gated by two separate Bearer token systems (see Authentication below). Neither has public self-service signup today -- both are issued by Sentinel Signal. Reach out from the pricing page to request access, and mention which surface you need: one-off audits, or recurring Watch monitoring.
- Pricing and contact: /pricing
2. Choose the required scope
Each route requires a specific scope on the token you were issued. Ask for the narrowest scope your integration needs -- see Authentication for the exact scope names.
3. Send the token as a Bearer header
Every authenticated Verify route reads the token from the Authorization header only. Tokens are never accepted as a query parameter, and must never be committed to source control.
- Authorization: Bearer <token>
4. Make a minimal request
A minimal Agent Readiness Audit call:
curl -X POST \
https://verify.sentinelsignal.io/v1/audits/readiness \
-H "Authorization: Bearer $TOKEN" \
-H "Content-Type: application/json" \
-d '{
"target": {
"domain": "example.com"
}
}'5. Inspect the structured response
Every audit response carries the same top-level shape: a schemaVersion, an auditId, a status (success/partial/unreachable/unsupported/failed), the evaluation payload itself, and a provenance block identifying the Verify build that produced it. Read the full field list on the endpoint's own page rather than guessing from this example.