A source entered the workflow
Your logs capture the URL, tool and time of an action. That alone does not preserve observable source-rights or TDM declarations.
SOURCE-RIGHTS EVIDENCE FOR AI WORKFLOWS
Your AI records the source.
Can it show what the source declared?
Your pipeline may log the URL and action, yet miss the machine-readable rights declarations visible when the source was checked. That gap makes later review harder. AcqPath preserves verifiable observations beside your existing workflow.
Checking live API…System status ↗
AcqPath / observation exampleOBSERVE
// 01 · Source and intended use
resource: https://publisher.example/article
purpose: ai-input
// 02 · Bounded inspection
HTTPS · robots.txt · RSL signals
Source hash · observation time
Signed evidence · decision preview
// 03 · What your audit can retain
Observed evidence record
OBSERVE VERIFY YOUR POLICY
Observe the public webEligible HTTPS sources, safety-gated
Capture the missing contextDeclarations at observation time
Retain evidence with the actionSigned records and source provenance
Keep policy controlYour team makes the decision
01 / THE EVIDENCE GAP
The source URL is recorded.
The declarations may not be.
When an agent fetches content or a RAG pipeline ingests a page, its trace tells you where it came from. It may not retain what the source declared about machine use when it was checked.
The source may later change
A later visit may encounter different declarations or no usable metadata. Rechecking cannot reliably reconstruct the earlier observation.
Review begins with missing context
When someone asks what restrictions were visible, your team may have to investigate without an evidence record tied to the earlier check.
02 / THE SOLUTION
Preserve what the source declared.
Keep the decision yours.
AcqPath checks available machine-readable rights signals for a declared purpose and preserves the observed result, provenance and uncertainty. Your tools and policies stay in control.
See what could be observed
Check eligible public HTTPS sources for relevant rights/TDM signals. Capture restrictions, license conditions or the absence of usable evidence.
Explore coverage ↗Make the observation verifiable
Keep a signed, timestamped record alongside source hashes and provenance, ready for later review or revalidation.
Explore a report ↗Preserve your workflow
Attach an evidence record to an agent trace, crawler output or RAG provenance. Your system remains responsible for any allow, deny or review decision.
Partner integration kit ↗03 / THE DIFFERENCE
From a URL in a log.
To a source-rights record.
An observation adds information the ordinary URL trace may not contain. The two records below illustrate the difference, not a real publisher check.
You can identify the source.
Resource: publisher.example/article
Action: AI ingestion
Declared restrictions at check time: Not recorded in this example.
You may know which URL was used without having preserved its machine-readable usage declarations.
You can review what was observed.
Resource + purpose: URL and ai-input
Illustrative result: LICENSE_REQUIRED
Evidence: Observation time, source hash, signed record.
A reviewer can inspect the observation, its provenance and its limits. The customer still determines what action is permitted.
Illustrative example only, not a live report for publisher.example. A meaningful check may return UNKNOWN or unavailable instead. No observed result is a license or legal clearance.
BUILT FOR YOUR WORKFLOW
For the teams that need
answers after ingestion.
Preserve observed source-rights context wherever a URL enters an agent, dataset or downstream decision.
What did the page declare when the agent checked it?
Keep source-rights evidence alongside tool traces so later reviews do not depend on the URL alone.
Explore agent integrations ↗Keep rights evidence with document provenance.
Capture what was observable before content enters a corpus, then retain it with the ingestion record.
Explore RAG integrations ↗Let downstream teams review source context.
Attach observations beside collected URLs, including restrictions, licensing signals and unresolved gaps.
Explore crawler integrations ↗04 / COVERAGE
Go beyond a fixed domain list.
Check more of the public web.
Inspect eligible public HTTPS URLs with Secure Preflight and Gateway. Bring source-rights observations into more web workflows without maintaining a fixed origin list.
When a source exposes no usable declaration, AcqPath preserves the uncertainty as UNKNOWN or an unavailable observation, rather than guessing. Your system keeps the final policy decision.
PUBLIC WEB COVERAGEGo beyond pre-approved domains.
Eligible public HTTPS sources with safety-gated inspection.
SOURCE-RIGHTS EVIDENCEFrom source signals to signed evidence.
Observed declarations, timestamps and verifiable provenance.
X402 INTEGRATIONPay per report. Integrate with confidence.
Transparent pricing and a separate purchase-verified Stock x402 route.
05 / INTEGRATE
Fits your workflow.
Not the other way around.
Add signed source-rights context where your team already works: MCP tools, web agents, crawlers and RAG pipelines. Keep the existing tool result and your own policy engine.
POST/v1/rights/preflightSECURE X402
{
"resource": "https://example.com/",
"purpose": "ai-input",
"tier": "fresh",
"max_total_micro": "20000"
}Prepare → inspect signed offer → authorized x402 → verify delivery
01
Point to the source
Pass an eligible public URL and the intended use. A single API contract works across supported web workflows.
02
See what you are buying
Review the observed decision preview, limitations and exact price before authorizing a paid report.
03
Bring evidence into your system
Verify the signed report and attach its evidence reference to your own logs, ingestion records or policy inputs.
06 / LIVE PRICING
Start with one report.
Know the price upfront.
Get verifiable source-rights evidence with clear per-report pricing. Review the decision preview and exact terms before authorizing any payment.
Rights PreflightFRESH
0.02 USDC / settled report
Inspect one eligible public source and receive signed evidence when available. Preview the outcome and price before paying.
View secure flow ↗Rights PreflightDEEP
0.05 USDC / settled report
Go deeper into available source metadata while retaining a signed, verifiable observation record.
All live pricing ↗Ingestion GateBATCH
0.06 USDC / fresh from
Bring source-rights evidence into multi-URL ingestion with one bounded operation and per-resource provenance.
Gateway contract ↗Payments currently use USDC on Base through x402. Secure Preflight supports eligible public HTTPS URLs; the separate Stock x402 route is reviewed-origin only. A prepared offer discloses the exact price, including a possible UNKNOWN diagnostic. Reports are evidence, not permission. Full terms and coverage ↗
BUILD ON A CLEAR EVIDENCE BOUNDARY
Keep the evidence.
Not just the URL.
Give your team a record of the declarations that were observable when a source was checked. Add AcqPath beside your existing tools and keep policy decisions under your control.