For AI agents

PayTransparency for agents

An MCP server and REST API that check job postings against every US pay-transparency law. An agent can look up the laws for free, then sign up, check postings and pay without a person in the loop.

Connect

MCP (Streamable HTTP): https://www.paytransparency.app/mcp. The law tools and signup work without a key; after signing up, reconnect with the key in the Authorization header.

{
  "mcpServers": {
    "paytransparency": {
      "type": "http",
      "url": "https://www.paytransparency.app/mcp",
      "headers": {
        "Authorization": "Bearer pt_live_..."
      }
    }
  }
}

REST: https://www.paytransparency.app/api/v1. Machine-readable: /openapi.json, /llms.txt, /.well-known/mcp.json.

Flow

Free: GET /api/v1/laws-for-employer?employee_count=120&states=CA,NY says which laws apply.
POST /api/v1/signup with { email, company_name, employee_count } returns an API key and starts a 14-day trial. The person at that email gets a link to claim the account.
POST /api/v1/check with a posting’s text or url. report.overallCompliant says whether it passes; report.stateResults lists what each law needs.
Fix what it flags and check again.

Pricing

One plan: $99 per 30 days, unlimited checks (120 an hour per key). 14-day trial, no card. Agents can pay with the Machine Payments Protocol: POST /api/v1/companies/{company_id}/pay answers 402 with a challenge, and paying it adds 30 days. Or get a Stripe Checkout link for a person with POST /api/v1/billing/checkout. GET /api/v1/billinglists what’s on.

Endpoints

GET /api/v1/laws (no key): Every pay-transparency law in the catalog, or one jurisdiction with ?state=CA. CC BY 4.0.
GET /api/v1/laws-for-employer (no key): The laws an employer of this size must follow where it hires: in effect now and upcoming, with a summary.
POST /api/v1/signup (no key): Create an account with a 14-day trial. Returns an API key (shown once). The person at email is sent a link to claim the account.
POST /api/v1/check: Check one job posting against every law that applies where it can be filled. Returns the report: overallCompliant, each law's result and the fine exposure. 120 an hour per key.
GET /api/v1/me: The account this key acts for, whether it's claimed, access dates and limits.
PATCH /api/v1/me: Change the employer's name or headcount.
POST /api/v1/claim: Email the owner a fresh link to claim the account in the dashboard.
GET /api/v1/keys: List active API keys.
POST /api/v1/keys: Create a key (returned once). Up to 5 active.
DELETE /api/v1/keys/{key_id}: Revoke a key.
GET /api/v1/billing: Trial and paid-through dates, and every way to pay that's switched on.
POST /api/v1/billing/checkout: A Stripe Checkout link for a person to subscribe at $99/month.
POST /api/v1/companies/{company_id}/pay (no key): Machine Payments Protocol: answers 402 with a challenge; pay it with an MPP client to buy 30 days for $99.00. No API key.

Errors are { error: { code, message } }. Limits: 120 requests a minute per key, 5 signups a day per network and 3 per email.

Hand this to your assistant

Use PayTransparency (https://www.paytransparency.app) to check our job postings for pay-transparency compliance.

1. Read https://www.paytransparency.app/llms.txt. If you support MCP, connect to https://www.paytransparency.app/mcp instead.
2. Sign up with my email [YOUR EMAIL], our company name and headcount. Keep the API key somewhere safe.
3. Check each of our open postings (I'll give you the URLs or text). Tell me which ones fail, which law, and what to add.
4. Draft the fixes for me to approve.

Fine print

The law data is licensed CC BY 4.0. Results summarize each statute and agency guidance; they aren’t legal advice. See the developer page for the embed and CSV, and the terms.