A source URL is only the start.
Keep the rights evidence.
Your agent may log the URL and action without preserving the machine-readable rights/TDM declarations visible when that URL was checked. AcqPath provides signed observations that can be retained beside the existing workflow. It does not grant a licence, establish ownership or decide whether your application may use content.
The secure Preflight and Gateway routes accept eligible public HTTPS origins through a signed, safety-gated relay. The four origins in live capabilities remain the separately reviewed origin set, not the total range of dynamically eligible sources. A fetch may produce UNKNOWN or an unavailable result. The Stock x402 compatibility route remains reviewed-origins-only.
1. Choose the right operation
| Endpoint | Buyer contract | Source scope |
|---|---|---|
POST /v1/rights/preflight | Secure x402 + AcqPath SIWX adapter | Dynamic public HTTPS |
POST /v1/rights/ingestion-gate | Secure x402 + AcqPath SIWX adapter | Dynamic, 1–4 URLs |
POST /v1/rights/revalidate | Secure x402 + prior signed checkpoint | Dynamic, one prior URL |
POST /v1/rights/preflight/x402 | Standard stock x402 v2, fresh only | Reviewed origins only |
Use the full developer quickstart, including the official TypeScript/Python client integrations. Do not send a custom or speculative payment signature.
2. Prepare a secure rights check
POST https://api.getacqpath.com/v1/rights/preflight
Content-Type: application/json
{
"resource": "https://example.com/",
"purpose": "ai-input",
"tier": "fresh",
"max_total_micro": "20000"
}The first valid request may return a prepared 402 Payment Required offer that includes the signed request binding, declared price and decision preview. For a meaningful public-source observation, UNKNOWN or no declaration may also be a priced diagnostic. A source/network outage with no usable observation is not a billable Preflight result.
The caller must explicitly supply purpose: ai-input, ai-index, ai-train or search. A partner-configured shadow default must be labeled as configured, not inferred from the end user. Crawl/access authorization remains separate from RSL usage declarations.
3. Check payment terms before authorizing
The secure endpoint requires the documented AcqPath SIWX/request-binding adapter with an official x402 signer, a persistent private operation/checkpoint and explicit payment consent. Verify the signing key, resource, network, asset, recipient, price, expiry and purpose independently. Never sign a second authorization after a timeout or an ambiguous settlement response. Resume the same operation.
For a standard x402 v2 buyer without SIWX, use the existing fixed Stock x402 endpoint; it is independently verified for 0.02 USDC fresh reports on the reviewed origins. Do not advertise it as dynamic HTTPS.
4. Verify delivery and decide in your system
Verify the signed report, source/purpose binding and the delivery proof. Keep the observed statement separate from your own application's allow, review or deny verdict. UNKNOWN means no conclusion about permission to use the resource.
For a portable data contract, use the provider-neutral Evidence Bridge. Existing tools can attach the verified evidence to an event, trace or ingestion record without changing behavior.
5. Understand boundaries and handling
Public HTTPS only; no private IP destinations, embedded credentials, arbitrary ports or query strings. Request counts and time budgets are bounded, DNS/IPs are validated, redirects are constrained and robots policies are respected. These safety checks are not a statement about legal rights.
Read our Data Handling & Processing Statement, Privacy and Terms. The published default for report retention is 30 days; no EU-only processing commitment is made.
Links and integration assets
Partner Integration Kit ↗ · Gateway ↗ · MCP setup ↗ · Live OpenAPI ↗ · Live capabilities ↗ · Evidence signing keys ↗.