Install Jentic One Beta
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Content Sweep Agent API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.
Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fcontentsweep.ai%2Fcontentsweep" | shStep 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fcontentsweep.ai%2Fcontentsweep" | sh
jentic register # connects your agent to your Jentic One instanceJentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.
What an agent can do with Content Sweep Agent API.
Register original works and partner-managed rights holders
Record revocable, scoped enforcement authority through delegations
Create expiring quotes and reserve prepaid credits for asynchronous enforcement operations
Read immutable evidence, cases, and takedown packets for an operation
Register webhook receivers and replay recorded events
GET STARTED
Rehearse the enforcement flow in a simulated sandbox before live activation
Patterns agents use Content Sweep Agent API for, with concrete tasks.
★ Copyright Registration and Authority
A rights holder's agent registers original works and records a revocable, scoped delegation that authorizes enforcement on their behalf. Authority is recorded explicitly and can be revoked irreversibly, so the chain of permission behind every later takedown is auditable.
Call POST /rights-holders to create the holder, POST /works to register the work, then POST /delegations to record scoped authority
Queued Takedown Enforcement
An agent prices an enforcement action with an expiring quote, reserves the quoted maximum in prepaid credits, and queues an asynchronous operation. It then polls the operation and reads the immutable evidence and takedown packet once the work completes.
Call POST /quotes for a price, POST /operations to reserve and queue the work, then GET /operations/{id} to poll completion
AI Agent Integration via Jentic
An AI agent reaches the Content Sweep Agent API through Jentic without handling the bearer key or the signing secrets itself. It searches by intent, receives the matching operation and its input schema, and executes the call with the credential injected at run time, rehearsing in the sandbox before any live, credit-spending action.
Search Jentic for 'register a copyright work', load the operation schema, and execute it with Jentic-managed credentials
35 endpoints — the content sweep agent api records copyright authority and runs takedown enforcement for registered works.
METHOD
PATH
DESCRIPTION
/rights-holders
Create a partner-managed rights holder
/works
Register an original work
/delegations
Record revocable scoped authority
/quotes
Create an expiring quote
/operations
Reserve a quote and queue asynchronous work
/operations/{id}
Poll a queued operation
/evidence/{id}
Export immutable evidence metadata and hash
/webhooks
Register a webhook receiver
/rights-holders
Create a partner-managed rights holder
/works
Register an original work
/delegations
Record revocable scoped authority
/quotes
Create an expiring quote
/operations
Reserve a quote and queue asynchronous work
/operations/{id}
Poll a queued operation
/evidence/{id}
Export immutable evidence metadata and hash
/webhooks
Register a webhook receiver
What agents get from Jentic-routed access to this vendor.
Setup
Wiring Content Sweep by hand means sending its bearer API key, handling expiring quotes and prepaid credit reservations, and storing the webhook signing secret that is returned only once. Through Jentic you install once, import Content Sweep from the API Directory, store the key once, and your agent calls it.
Permission scoping
A rule can confine your agent to the operations it needs, such as registering works and reading evidence, because the credit-spending and irreversible actions are separate operations you choose to include or leave out. Revoking a delegation or purchasing credits stays off the agent's reach unless you grant it.
Credential isolation
Your Content Sweep key is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.
Intent-based discovery
Agents search Jentic by intent such as 'register a copyright work' or 'queue a takedown', and Jentic returns the matching Content Sweep operation with its input schema so the agent calls the right endpoint without browsing the reference docs.
Alternatives and complements available in the Jentic catalogue.
Specific to using Content Sweep Agent API through Jentic.
What authentication does the Content Sweep Agent API use?
Most operations authenticate with a bearer API key in the Authorization header per the OpenAPI spec, and a short scoped access token can be exchanged for 15-minute use. A separate apiKey scheme, the Stripe-Signature header, secures the provider billing webhook, and several discovery endpoints such as capabilities and pricing are public. Through Jentic the key is stored encrypted by your own Jentic One instance and injected at execution time.
Can I queue a takedown enforcement action with the Content Sweep Agent API?
Yes. Create an expiring quote, reserve the quoted maximum in prepaid credits with the operations endpoint, and poll the operation until the evidence and takedown packet are ready. Enforcement requires an appointed delegation, so the authority behind each action is recorded first.
Does the Content Sweep Agent API offer a sandbox before live use?
Yes. The sandbox is simulated and lets an agent rehearse the enrollment and enforcement flow without spending credits, while actual operations use real quotes. Live capabilities depend on account activation, so an agent can validate its logic before switching to the accountable live organization.
How do I register a work through Jentic with the Content Sweep Agent API?
Search Jentic for 'register a copyright work', and it returns the Content Sweep work-registration operation with its input schema. Load the schema and execute POST /works with the credential injected at run time. To run it on your own infrastructure, install Jentic One from its GitHub repo.
Can I limit what my agent is allowed to do with the Content Sweep Agent API?
Yes. Write a rule that allows only the operations the agent needs, for example registering works and reading evidence, so credit-spending actions like reserving an enforcement operation or purchasing credits are left out unless you add them. Each call runs through your own instance and is logged for review.
For Agents
Register copyright works and rights holders, record scoped enforcement authority, queue takedown operations, and read back evidence and packets. Most calls use a bearer API key; a Stripe-Signature apiKey header secures the provider billing webhook.
Use for: Register an original work for a rights holder, Record a revocable, scoped delegation of enforcement authority, Create a quote and queue a takedown enforcement operation, Get the evidence and takedown packet for an operation
Not supported: Does not handle visual search, media capture, or guaranteed content removal. Use for recording copyright authority and queuing takedown enforcement only.
The Content Sweep Agent API records copyright authority and runs takedown enforcement for registered works. Rights holders register original works, record revocable scoped delegations, request expiring quotes, and queue asynchronous enforcement operations whose evidence, cases, and takedown packets can be read back. Prepaid credits meter usage, webhook receivers are registered with a signing secret returned once, and a simulated sandbox lets a caller rehearse the flow before live activation.
This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.
Base layer of spec validity and structural soundness.
Aggregated quality score from linter diagnostics, weighted by severity.
Percentage of `$ref` references that resolve successfully.
Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).
Structural correctness score based on schema issues using logarithmic dampening.
Clarity, completeness, and ingestion readiness for developers and tooling.
How richly the API is illustrated with examples.
Percentage of examples that conform to their schemas.
Percentage of operations with complete response definitions (success, client error, server error).
Health of API ingestion, bundling, and resolution within Jentic pipelines.
Semantic breadth, depth, and agent comprehension for AI systems.
Coverage of descriptions across API elements.
Coverage of RFC 9457 Problem Details for error responses.
Coverage, uniqueness, and casing consistency of operationIds for AI inference.
Coverage of summaries across operations/tags/info.
Functional utility, complexity comfort, and AI orchestration readiness.
Agent comfort level based on API operational and structural complexity.
Trust, risk posture, and security compliance.
Average quality of security schemes based on authentication method strength (weakest link for OAuth2).
Findability, semantic richness, and reasoning readiness.
Clarity and depth of descriptions across API elements.
Score it yourself
Every API in the directory is allowlisted, so you can re-score it with no key required.
npx @jentic/api-scorecard-cli score <openapi-url>