RegLayer for agents

Get regulatory research through an API.

Ask a regulatory question with an Instant Brief, or screen supplied working materials with Check. Each response includes structured JSON and a PDF.

View quickstart OpenAPI →

Instant Brief

$0.99 USD

One source-backed answer for a concrete regulatory question.

instant_brief

Check

$0.99 USD

Screen one or two supplied materials for regulatory issues and changes to consider.

instant_check

Machine payment

HTTP 402

Pay from the first request with a Stripe Shared Payment Token.

stripe/charge

Access and delivery

One request. Private retrieval.

Choose the product

Use a Brief for a question. Use a Check when the user supplies material to screen.

Submit and pay

The API returns an HTTP 402 payment challenge. Retry the same request with a Stripe Shared Payment Token.

Close and poll

After HTTP 202, do not hold the request open. Store the order ID and private access token, then poll the status URL every 20 seconds.

Retrieve the work

When status is ready, retrieve the structured findings or PDF with the same bearer token. Email access is not required.

In development

Keep agents inside a changing regulatory perimeter.

RegLayer is exploring an operational regulatory context layer for agents. It would connect an agent's permitted workflows, disclosures, data use, actions, and operating markets to the company's maintained regulatory perimeter.

Detect impact

Identify which agent workflows may be affected when a rule, business fact, market, or agent capability changes.

Propose controls

Surface the disclosure, data-use, approval, or workflow control that may need to change.

Preserve review

Keep material decisions visible to accountable humans, with sources and uncertainty attached.

This operational context layer is a future product direction. The current Agent API supports Instant Briefs and Check.

Quickstart

Start with the product catalogue.

GET https://reglayer.com/api/agent/v1/products

POST https://reglayer.com/api/agent/v1/instant-briefs
Content-Type: application/json
Idempotency-Key: your-stable-id
RegLayer-Agent-Id: your-stable-agent-id

{
  "product": "instant_brief",
  "email": "operator@example.com",
  "name": "Research Agent",
  "company_name": "Example Company",
  "question": "What should this company address before launch?",
  "decision_context": "The company plans to launch its product next quarter.",
  "product_context": "Describe the product, users, data, and operating model.",
  "jurisdictions": ["United States (federal)"],
  "terms_accepted": true
}

For Check, post to /api/agent/v1/checks with product: "instant_check" and a materials array containing one or two objects with filename and readable content. Combined material is capped at approximately 60,000 tokens.

The first request returns HTTP 402 with the applicable payment challenge. Retain the RegLayer-Order-Id and RegLayer-Access-Token headers. The access token is shown once and is required for status, structured result, and PDF retrieval.

OpenAPIMachine-readable REST contract llms.txtCompact discovery file MCP endpointProduct discovery and private retrieval tools Product catalogueCurrent prices, limits, and delivery

Scope

Purposefully narrow.

This release supports system-generated Instant Briefs and Check. It does not expose the RegLayer workspace, account data, or Expert Brief service. Policy research and regulatory intelligence; not legal advice.