AcqPath — RSL rights preflight for AI and RAG

Check observed content-use declarations before AI input, RAG indexing, training or search. AcqPath returns signed evidence of observed RSL declarations for supported URLs. It does not grant a license, establish ownership or provide legal clearance. UNKNOWN never authorizes ingestion.

Start integrating · Supported scope · Examples · MCP Registry · Smithery · Glama

Fresh 0.02 USDC; deep 0.05 USDC, observed 2026-09-10. Read live capabilities and verify the signed quote before authorizing payment. Current origin coverage is exactly https://medium.com, https://theguardian.com, https://rslstandard.org, and https://rslcollective.org. Coverage is not a promise that every URL returns a purchasable or permissive report.

Connect once

For clients supporting remote HTTP MCP configuration:

{"mcpServers":{"acqpath":{"url":"https://api.getacqpath.com/mcp"}}}

Client-specific configuration includes VS Code and the supported Streamable HTTP transport. Use acqpath_capabilities first. acqpath_rights_quote can prepare a quote and consume metadata quota. The upstream legacy acqpath_quote routing tool is disabled; exclude it in your client.

MCP prepares quotes. Paid report delivery uses HTTP x402 outside MCP. Quote claims belong in private application state, outside model context, telemetry and gateway logs. Do not enable blanket tool approval.

Related MCP server: @costrinity/vitna-compliance-mcp

Integrate a reusable evidence gate

JavaScript gate · TypeScript workflows · Python read-only example · Full seven-step flow

1. Check current origin coverage and select the downstream purpose.

2. Create one quote for one stable job ID; hold unsupported/UNKNOWN outcomes.

3. Verify the signed offer and its exact URL, recipient, network, asset and amount.

4. Use a buyer-controlled signer with an explicit finite task budget; persist an encrypted checkpoint before submission.

5. Retrieve over HTTP x402; verify report, receipt and delivery binding.

6. After ambiguous submission, resume the same checkpoint and authorization. Never blindly create a second payment.

7. Keep the evidence and private recovery state separate from application permission. Even ALLOW_DECLARED requires an application policy decision.

The client is available as reviewed source in packages/rights-client. npm publication is on owner hold; do not attempt an npm install of this unpublished package. Examples use repository-relative imports. No separate Python payment SDK is claimed.

Machine-readable integration reference

llms.txt · Full reference · OpenAPI subset · Discovery profile · Pricing snapshot · Agent skill

The public skill describes when and how to integrate; it never authorizes spending. Its source is ready for compatible skills clients. Presence in this repository is not proof of ranking in a skills directory.

Verification and operating scope

This repository contains distribution documentation and the client, not the production backend. Node 22.16+ is required; no root runtime dependencies or install step is needed for tests/build. Maintainer commands are documented in the execution plan.

Daily public discovery verification checks public metadata, docs and links without quotes, wallets or operator secrets. A GitHub push runs CI; the isolated Cloudflare Pages project uses a separate reviewed direct upload.

Channel matrix · Discovery tests · Bazaar compatibility · Revenue baseline · Revenue analysis · Acceptance

The SDK's MIT license applies only to its client package. No blanket license is granted to the backend, service output or publishers' content. The distribution root remains UNLICENSED. No real payment, wallet signature, independent customer or organic revenue is claimed by this release.

Documentation for coding agents

The public integration skill and full machine reference describe the private buyer flow. A separate GitMCP documentation endpoint exposes this public repository as searchable context; it does not execute or replace the paid AcqPath service. Its metadata connection was verified; search quality is recorded separately in DISCOVERY-TESTS.md.

Common integration questions

Can I use this page for RAG? AcqPath can report observed RSL declarations for a supported page. Use ai-index for corpus indexing and separately evaluate ai-input when supplying content to a model. UNKNOWN, unsupported coverage and license-required outcomes hold ingestion. Signed evidence supports your own policy decision; it does not grant permission or replace a license.

Where do I check machine-readable usage restrictions? Read the current capabilities, then prepare an RSL rights quote for the actual purpose and supported origin. The private HTTP/x402 integration obtains and verifies the signed report. AcqPath does not prove ownership or legal clearance, and crawl/robots policy remains a separate check.