Install Jentic One Beta

Connect the PolicyForge API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the PolicyForge 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%2Fpolicyforge.co%2Fpolicyforge" | sh

Step 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%2Fpolicyforge.co%2Fpolicyforge" | sh
jentic register       # connects your agent to your Jentic One instance

Jentic 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.

Capabilities

What an agent can do with PolicyForge API.

Generate a privacy policy, terms of service, cookie policy, or refund policy draft from business_type, jurisdiction, and data_collection inputs

Edit a policy's title or content and move it between draft, published, and archived status

Turn on hosting_enabled to publish a policy on a PolicyForge-hosted page

Record a visitor's consent choices per category against a policy_version

GET STARTED

Start building with PolicyForge API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use PolicyForge API for, with concrete tasks.

★ Agent-drafted policies through Jentic

A developer launching a new product asks their agent for a privacy policy that matches the stack. Through Jentic the agent finds the PolicyForge generate operation by intent, fills type, business_type, jurisdiction, company_name, and contact_email, and returns a draft for human review. The bearer key is injected at call time, so the agent never holds it, and a rule can keep it to drafting and reading without the delete operations.

Call POST /api/v1/policies with type privacy_policy, business_type saas, jurisdiction gdpr, company_name Acme Inc, and contact_email privacy@acme.com, then fetch the draft with GET /api/v1/policies/{policyId}

Publish and host a reviewed policy

Once a lawyer or founder has reviewed a draft, the policy needs to go live at a stable URL. PolicyForge lets a client update the title or content, set status to published, and switch hosting_enabled on so the policy is served from a PolicyForge-hosted page. Archiving an outdated version keeps the history without deleting it.

Call PATCH /api/v1/policies/{policyId} with status published and hosting_enabled true, then confirm the change with GET /api/v1/policies/{policyId}

Consent logging at checkout

A checkout flow must prove that each buyer agreed to the terms in force at the time. POST /api/v1/consent stores the visitor's user_id, the policy_version, a map of consent categories, and optional ip_address and user_agent for the audit trail. Records tied to a policy_id show up under that policy and can be filtered later.

Call POST /api/v1/consent with user_id visitor_abc123, policy_version v2.1, and consents essential true, analytics true, marketing false

Consent audit and erasure requests

When a regulator or customer asks for proof of consent, the consent list can be filtered by end_user_id, policy_id, banner_config_id, consent source, and a from and to date range, with cursor pagination up to 200 records per page. For an erasure request, a single consent record can be removed by its record id.

Call GET /api/v1/consent with end_user_id visitor_abc123, page through next_cursor, and report each recorded consent map

Key Endpoints

10 endpoints — the policyforge api generates draft privacy policies, terms of service, cookie policies, and refund policies from a short description of your business, its jurisdiction, and the data it collects.

METHOD

PATH

DESCRIPTION

POST

/api/v1/policies

Generate a policy draft

GET

/api/v1/policies

List policies with status and type filters

GET

/api/v1/policies/{policyId}

Get a policy with content and hosting info

PATCH

/api/v1/policies/{policyId}

Update title, content, status, or hosting

POST

/api/v1/consent

Record visitor consent

GET

/api/v1/consent

List and filter consent records

GET

/api/v1/consent/{userId}

Get consent records for a visitor

POST

/api/v1/policies

Generate a policy draft

GET

/api/v1/policies

List policies with status and type filters

GET

/api/v1/policies/{policyId}

Get a policy with content and hosting info

PATCH

/api/v1/policies/{policyId}

Update title, content, status, or hosting

POST

/api/v1/consent

Record visitor consent

GET

/api/v1/consent

List and filter consent records

GET

/api/v1/consent/{userId}

Get consent records for a visitor

Why Jentic?

What agents get from Jentic-routed access to this vendor.

Setup

Wiring PolicyForge by hand means minting a pf_live_ key in the dashboard, sending it as a bearer token, handling per-tier X-RateLimit headers, and remembering that the hosted-consent endpoint takes no key at all. Through Jentic you install once, import PolicyForge from the API Directory, store the key once, and your agent calls it.

Permission scoping

PolicyForge puts the policy id in the URL path (/api/v1/policies/{policyId}), so a rule can pin your agent to one policy and the operations you pick. You choose what it may call, so destructive ones like deleting a policy or deleting consent records are not included unless you add them.

Credential isolation

Your PolicyForge API 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 'generate a privacy policy' or 'look up consent for a visitor', and Jentic returns the matching PolicyForge operation with its input schema, including the type and jurisdiction enums, so the agent fills the request correctly.

FAQs

Specific to using PolicyForge API through Jentic.

What authentication does the PolicyForge API use?

The PolicyForge API authenticates with a bearer token per its OpenAPI spec: you generate an API key in the PolicyForge API Dashboard and send it in the Authorization header as Bearer pf_live_.... One endpoint, POST /api/v1/consent/policy/{policyId}/record, is public and needs no key because the owner is derived from the hosted policy. Through Jentic the key is stored by your own instance and attached at call time.

Can I generate a GDPR privacy policy with the PolicyForge API?

Yes. POST /api/v1/policies takes a type such as privacy_policy, terms_of_service, cookie_policy, or refund, a business_type, a jurisdiction such as gdpr, ccpa, or uk, plus company_name and contact_email. Optional fields like data_collection, third_party_integrations, and data_retention shape the draft. PolicyForge notes that generated content is not legal advice, so review it before publishing.

What are the rate limits for the PolicyForge API?

The PolicyForge OpenAPI spec lists per-tier limits: Free at 10 requests per minute and 100 per day, Pro at 60 per minute and 5,000 per day, and Enterprise at 300 per minute and 50,000 per day. Every response includes X-RateLimit-Limit, X-RateLimit-Remaining, and X-RateLimit-Reset headers so a client can back off before hitting the ceiling.

Is there a PolicyForge MCP server?

You don't need an MCP server to give your agent PolicyForge. Jentic connects it directly from the API Directory: import it, store your API key once, and your agent calls the policy and consent operations it needs, discovered on demand rather than loaded into its context up front.

Can I limit what my agent is allowed to do with PolicyForge?

Yes. For example, write a rule that allows only POST /api/v1/policies and GET /api/v1/policies/{policyId}, so the agent can draft and read policies but cannot publish, delete, or touch consent records. Because policy ids sit in the URL path, you can also pin the update operation to one policyId, and every call the agent makes is logged.

How do I record visitor consent with PolicyForge through Jentic?

Search Jentic for 'record user consent for a privacy policy', load the POST /api/v1/consent operation, and send user_id, policy_version, and a consents map such as essential true and marketing false, optionally with a policy_id. To run it on your own infrastructure, install Jentic One from its GitHub repo.

PolicyForge API

AI ReadinessAI-Aware (A-)71/100

See full scorecard

Official vendor OpenAPI document · agent-readySecurityCompliancebearer10 EndpointsREST

For Agents

Generate privacy, terms, cookie, and refund policy drafts for a business, publish and host them, and record or look up visitor consent records for compliance audits.

Use for: I need to generate a GDPR privacy policy for my SaaS product, Create a cookie policy draft for an e-commerce site under CCPA, List all published policies on my account, Record that a visitor accepted analytics cookies but rejected marketing

Not supported: Does not provide legal advice, run cookie scanning, or manage security compliance frameworks such as SOC 2. Use for generating and hosting policy documents and recording visitor consent only.

The PolicyForge API generates draft privacy policies, terms of service, cookie policies, and refund policies from a short description of your business, its jurisdiction, and the data it collects. Drafts can be retrieved, edited, published, and hosted on a PolicyForge page, and every policy carries a lifecycle status of draft, published, or archived. A consent ledger records which cookie and data categories each website visitor accepted, filterable by policy, banner, source, and date for later compliance audits. Generated content is not legal advice and should be reviewed before publication.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: A+Signals: 4

98%

Lint Results

Aggregated quality score from linter diagnostics, weighted by severity.

100%

Resolution Completeness

Percentage of `$ref` references that resolve successfully.

100%

Specification Validity

Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).

75%

Structural Integrity

Structural correctness score based on schema issues using logarithmic dampening.

Developer Experience & Jentic Compatibility

Clarity, completeness, and ingestion readiness for developers and tooling.

Grade: BSignals: 4

15%

Example Density

How richly the API is illustrated with examples.

100%

Example Validity

Percentage of examples that conform to their schemas.

53%

Response Coverage

Percentage of operations with complete response definitions (success, client error, server error).

100%

Tooling Readiness

Health of API ingestion, bundling, and resolution within Jentic pipelines.

AI-Readiness & Agent Experience

Semantic breadth, depth, and agent comprehension for AI systems.

Grade: CSignals: 4

48%

Description Coverage

Coverage of descriptions across API elements.

Error Standardization

Coverage of RFC 9457 Problem Details for error responses.

100%

OperationId Quality

Coverage, uniqueness, and casing consistency of operationIds for AI inference.

77%

Summary Coverage

Coverage of summaries across operations/tags/info.

Agent Usability

Functional utility, complexity comfort, and AI orchestration readiness.

Grade: A+Signals: 1

94%

Complexity Comfort

Agent comfort level based on API operational and structural complexity.

Security

Trust, risk posture, and security compliance.

Grade: B-Signals: 1

60%

Authentication Strength

Average quality of security schemes based on authentication method strength (weakest link for OAuth2).

AI Discoverability

Findability, semantic richness, and reasoning readiness.

Grade: A-Signals: 1

79%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the PolicyForge API to your agent

Capabilities

Start building with PolicyForge API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

PolicyForge API

Jentic AI Readiness Score

PolicyForge API

Foundational Compliance

Lint Results

Resolution Completeness

Specification Validity

Structural Integrity

Developer Experience & Jentic Compatibility

Example Density

Example Validity

Response Coverage

Tooling Readiness

AI-Readiness & Agent Experience

Description Coverage

Error Standardization

OperationId Quality

Summary Coverage

Agent Usability

Complexity Comfort

Security

Authentication Strength

AI Discoverability

Descriptive Richness