{
  "meta": {
    "attribution": "Anchor Terminal (https://www.anchorterminal.com)",
    "docs": "https://www.anchorterminal.com/docs/",
    "generatedAt": "2026-10-08",
    "license": "CC-BY-4.0",
    "method": "https://www.anchorterminal.com/benchmark/",
    "methodology": "0.4",
    "openapi": "https://www.anchorterminal.com/openapi.json",
    "preview": false,
    "run": "2026-10-01",
    "runLabel": "October 2026 research run"
  },
  "tool": {
    "slug": "bill",
    "name": "BILL",
    "vendor": "BILL Holdings, Inc.",
    "vendorUrl": "https://www.bill.com",
    "kind": "http-api",
    "category": "spend-management",
    "summary": "BILL is a US financial operations platform for accounts payable, accounts receivable and company card spend. Its v3 REST API reads and writes bills, payments, invoices, budgets, cards, transactions and reimbursements, and an MCP server in beta gives read-only access.",
    "url": "https://www.anchorterminal.com/tools/bill",
    "markdownUrl": "https://www.anchorterminal.com/tools/bill.md",
    "slimMarkdownUrl": "https://www.anchorterminal.com/tools/bill.min.md",
    "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/bill.json",
    "license": "Proprietary service under the BILL Developer Terms and the BILL General Terms of Service",
    "transports": [
      "http"
    ],
    "remoteUrl": "https://gateway.prod.bill.com/connect",
    "packages": [],
    "auth": "mixed",
    "authNotes": "Access is self-serve. A person signs up for a sandbox or production account in a browser and generates a developer key under Settings \u003e Sync \u0026 Integrations \u003e Manage Developer Keys after accepting the Developer Terms. The AP and AR API signs in with `POST /v3/login` using a username, password, organisation ID and `devKey`, and returns a `sessionId` that expires after 35 minutes idle and carries the user's role, with no scopes. Payments and bank account changes need a session trusted by multi-factor authentication. The Spend \u0026 Expense API takes an `apiToken` header that an ADMIN user generates, with no login. App partners request their developer key by email and use customer sync tokens that can't make payments. The MCP server uses OAuth through auth.bill.com with PKCE, and clients other than Claude and ChatGPT need approval by email.",
    "pricing": "freemium",
    "pricingNotes": "No separate API fee is published. bill.com/product/pricing lists API access on every plan. AP and AR plans are Essentials at $49, Team at $65 and Corporate at $89 per user per month, with Enterprise on request, and Spend \u0026 Expense at $0 per user per month, which needs an approved credit application. Payment types such as cheques, ACH and international transfers carry per-transaction fees. The sandbox is self-serve and free, and production has a 30-day trial. The Developer Terms mention API licence and development fees set on the developer site or an order form (checked 2026-10-08).",
    "priceSummary": "$49 / seat-mo",
    "where": "hosted",
    "x402": {
      "level": "no",
      "evidence": "No x402, MPP or L402 in the developer docs, the OpenAPI files or the pricing page (checked 2026-10-08).",
      "endpoints": []
    },
    "toolCount": null,
    "popularity": {
      "githubStars": null,
      "npmWeekly": null,
      "pypiWeekly": null,
      "asOf": "2026-10-08"
    },
    "docsUrl": "https://developer.bill.com/docs/home",
    "llmsTxt": "https://developer.bill.com/llms.txt",
    "openapi": "https://developer.bill.com/openapi/bill-v3-api.json",
    "capabilities": [
      "spend.transactions",
      "spend.expenses",
      "spend.cards",
      "spend.bills",
      "accounting.invoices"
    ],
    "tags": [
      "hosted",
      "freemium",
      "api-key",
      "oauth",
      "mcp",
      "openapi",
      "llms-txt",
      "webhooks",
      "sandbox",
      "status-page",
      "soc2"
    ],
    "lastRelease": "2026-05-21",
    "graded": true,
    "anchor": {
      "graded": true,
      "score": 60.9,
      "grade": "C",
      "agentReady": false,
      "rank": 380,
      "ranked": true,
      "rankOf": 722,
      "categoryRank": 5,
      "methodology": "0.4",
      "run": "2026-10-01",
      "scores": {
        "ergonomics": 60,
        "maintenance": 32,
        "payments": 25,
        "reliability": 81,
        "schema": 83,
        "security": 56,
        "transparency": 66
      },
      "pending": [
        "performance",
        "tasks"
      ],
      "breakdown": [
        {
          "key": "reliability",
          "name": "Reliability",
          "weight": 16,
          "effectiveWeight": 20,
          "score": 81,
          "points": 16.2,
          "reason": "Read with the hosted lines and scored on the v3 REST API. A Statuspage site at www.billcomstatus.com has 15 components, among them API Servers, Virtual Card and Multi-Factor Authentication (20). Its incident feed shows nothing after 15 April 2026, so the last 90 days are clean (30). Limits are published with numbers, 20,000 requests an hour per developer key, three concurrent per key per organisation, 200 logins an hour and 60 Spend \u0026 Expense calls a minute per token (15). The docs give the two limit errors, `BDC_1144` and `BDC_1322`, and a backoff example in Python. No Retry-After header is documented, and no idempotency key is accepted on the v3 API's write operations, payments included (7 of 15). The docs say production is backed by SLAs, but no SLA document was found and the General Terms of Service supply the service as is (0). The v3 API is generally available. The MCP server is beta (9 of 10)."
        },
        {
          "key": "performance",
          "name": "Performance",
          "weight": 10,
          "effectiveWeight": 0,
          "pending": true,
          "points": 0,
          "reason": "Pending. Latency is measured per call by our probes, which haven't run yet, so this run doesn't score it. Its weight is shared across the assessed categories until the first probe window closes."
        },
        {
          "key": "schema",
          "name": "Schema \u0026 documentation",
          "weight": 13,
          "effectiveWeight": 16.25,
          "score": 83,
          "points": 13.49,
          "reason": "Two public OpenAPI 3.0.1 files, `bill-v3-api.json` with 314 operations and `connect-events-api.json` with 12 (25). llms.txt, a Markdown copy of every page and a docs MCP server (10). Every operation has a summary and a description, with a median of 209 characters, links to the guide and notes such as the MFA requirement on payments. Few say when not to call an endpoint (14 of 20). 110 enums, 499 required lists, 271 formats, 82 length limits and 32 patterns. The spec declares no security schemes, so credentials appear as header parameters, and `filters` is a string with its own syntax (11 of 15). 1,025 examples. Errors are documented as one `4XX` and one `5XX` array on 311 operations, with 12 common codes explained and over 500 left to the v2 `Errors.json` call (10 of 15). The path is versioned v3 and the changelog is dated with an RSS feed. Its latest entry is 21 May 2026, and the MCP server, whose guide was updated on 6 October, has no entry (13 of 15)."
        },
        {
          "key": "ergonomics",
          "name": "Agent ergonomics",
          "weight": 13,
          "effectiveWeight": 16.25,
          "score": 60,
          "points": 9.75,
          "reason": "`max` sizes a page, with a default of 20 and a ceiling of 100 on AP and AR lists and 50 on Spend \u0026 Expense lists. No field selection was found (16 of 25). Lists return `nextPage` and `prevPage` cursors and take `filters` with nine operators, including ranges on `createdTime` and `updatedTime`, and `sort` (19 of 20). Errors are an array of objects with a `BDC_` code, severity, category and message, and the common codes page gives a fix for each of 12 codes. Rate limit errors don't state when to retry (15 of 20). No idempotency key on the 203 write operations of the v3 API. `X-Idempotent-Key` is accepted on two webhook subscription calls, and a bulk payment request succeeds or fails as a whole. The MCP server is read-only, and its tool annotations couldn't be read without an account (5 of 20). AP and AR calls need a login first and two headers on every call, and the session ends after 35 minutes idle. No official SDK was found, only a Postman collection (5 of 15)."
        },
        {
          "key": "security",
          "name": "Security \u0026 auth",
          "weight": 14,
          "effectiveWeight": 17.5,
          "score": 56,
          "points": 9.8,
          "reason": "The AP and AR API signs in with a user's username and password plus a developer key, sent in the request body, and the session carries that user's role with no scopes. The Spend \u0026 Expense API takes a token an ADMIN user generates, with no scopes documented. Sync tokens for app partners can't make payments. The MCP server uses OAuth with PKCE (S256) and a revocation endpoint, with only `openid` and `offline_access` as scopes. No secret travels in a URL (16 of 30). Creating a payment, adding a funding bank account and enabling vendor auto-pay need a session trusted by multi-factor authentication, user roles limit who can pay, bill approval policies are in the API, and the MCP server is read-only. No confirmation step was found for other writes, such as creating a vendor card (16 of 20). Bill and invoice text, vendor names and memos are untrusted content, and no prompt-injection guidance was found (3 of 15). An audit trail endpoint covers vendor creates and edits with the user and source, and users can review and disconnect MCP connections under Connected apps. No audit endpoint for other objects or for API calls was found (7 of 15). Annual SOC 1 and SOC 2 Type II audits and a vulnerability disclosure programme on HackerOne. No bounty is stated and security.txt returns 404 (14 of 20)."
        },
        {
          "key": "payments",
          "name": "Payments \u0026 pricing",
          "weight": 10,
          "effectiveWeight": 12.5,
          "score": 25,
          "points": 3.13,
          "reason": "Read with the hosted rubric. No x402, MPP or L402 (0). Plan prices are public, $49, $65 and $89 per user per month for AP and AR and $0 for Spend \u0026 Expense, with API access listed on each. The API has no per-call price, and the per-transaction payment fees aren't on the pricing page we read (10). The sandbox is self-serve, charges no subscription fee and uses a test bank account or test card. Production has a 30-day trial, and whether it needs a payment card wasn't established, so partial credit (15 of 20). A person signs up in a browser and generates the developer key in the web app (0)."
        },
        {
          "key": "tasks",
          "name": "Task success",
          "weight": 10,
          "effectiveWeight": 0,
          "pending": true,
          "points": 0,
          "reason": "Pending. Task success needs the category task suites run through each tool, which haven't run yet, so this run doesn't score it. Its weight is shared across the assessed categories until then. A data provider's data-quality score is published on its listing now and becomes half of this category when it's scored."
        },
        {
          "key": "maintenance",
          "name": "Maintenance \u0026 community",
          "weight": 7,
          "effectiveWeight": 8.75,
          "score": 32,
          "points": 2.8,
          "reason": "The changelog's latest dated entry is 21 May 2026, 140 days before the check. The docs platform's metadata shows `bill-v3-api.json` updated on 5 October 2026 and the MCP server guide on 6 October, so the API is still changing without dated notes (20 of 30). No dated changelog entry falls in the last 90 days (0). Closed service with a changelog, an RSS feed and a developer programme email address. Response times couldn't be observed, and the changelog has been silent for over four months (7 of 15). No official SDK was found, and the MCP server isn't in the official MCP registry, as its own guide says of connector directories. A Postman collection is published (2 of 15). There is no package to assess. The spec and docs are current (3 of 10)."
        },
        {
          "key": "transparency",
          "name": "Transparency \u0026 trust",
          "weight": 7,
          "effectiveWeight": 8.75,
          "score": 66,
          "points": 5.78,
          "note": "editorial 44, provenance 88",
          "reason": "Closed service with terms at stable URLs, the Developer Terms (effective 3 March 2026) and the General Terms of Service (last updated 10 February 2025) (15 of 30). The Privacy Notice (effective 30 January 2026) covers the products and describes retention by criteria without fixed periods. No data processing agreement was found on the legal index, and no statement on training models with customer data was found in the notice (12 of 30). The Developer Terms commit BILL to commercially reasonable efforts at 30 days' notice of deprecations and breaking changes, and the same document keeps the right to change or discontinue the API at any time. The MFA phone change of 3 April 2026 was announced on 6 February, and the FAQ says there are no plans to deprecate v2 (14 of 20). No sub-processor list or data location statement was found. The legal index has a bank partners page (3 of 20)."
        }
      ],
      "assessment": {
        "date": "2026-10-08",
        "basis": "public evidence",
        "confidence": "medium",
        "notes": {
          "ergonomics": "`max` sizes a page, with a default of 20 and a ceiling of 100 on AP and AR lists and 50 on Spend \u0026 Expense lists. No field selection was found (16 of 25). Lists return `nextPage` and `prevPage` cursors and take `filters` with nine operators, including ranges on `createdTime` and `updatedTime`, and `sort` (19 of 20). Errors are an array of objects with a `BDC_` code, severity, category and message, and the common codes page gives a fix for each of 12 codes. Rate limit errors don't state when to retry (15 of 20). No idempotency key on the 203 write operations of the v3 API. `X-Idempotent-Key` is accepted on two webhook subscription calls, and a bulk payment request succeeds or fails as a whole. The MCP server is read-only, and its tool annotations couldn't be read without an account (5 of 20). AP and AR calls need a login first and two headers on every call, and the session ends after 35 minutes idle. No official SDK was found, only a Postman collection (5 of 15).",
          "maintenance": "The changelog's latest dated entry is 21 May 2026, 140 days before the check. The docs platform's metadata shows `bill-v3-api.json` updated on 5 October 2026 and the MCP server guide on 6 October, so the API is still changing without dated notes (20 of 30). No dated changelog entry falls in the last 90 days (0). Closed service with a changelog, an RSS feed and a developer programme email address. Response times couldn't be observed, and the changelog has been silent for over four months (7 of 15). No official SDK was found, and the MCP server isn't in the official MCP registry, as its own guide says of connector directories. A Postman collection is published (2 of 15). There is no package to assess. The spec and docs are current (3 of 10).",
          "payments": "Read with the hosted rubric. No x402, MPP or L402 (0). Plan prices are public, $49, $65 and $89 per user per month for AP and AR and $0 for Spend \u0026 Expense, with API access listed on each. The API has no per-call price, and the per-transaction payment fees aren't on the pricing page we read (10). The sandbox is self-serve, charges no subscription fee and uses a test bank account or test card. Production has a 30-day trial, and whether it needs a payment card wasn't established, so partial credit (15 of 20). A person signs up in a browser and generates the developer key in the web app (0).",
          "reliability": "Read with the hosted lines and scored on the v3 REST API. A Statuspage site at www.billcomstatus.com has 15 components, among them API Servers, Virtual Card and Multi-Factor Authentication (20). Its incident feed shows nothing after 15 April 2026, so the last 90 days are clean (30). Limits are published with numbers, 20,000 requests an hour per developer key, three concurrent per key per organisation, 200 logins an hour and 60 Spend \u0026 Expense calls a minute per token (15). The docs give the two limit errors, `BDC_1144` and `BDC_1322`, and a backoff example in Python. No Retry-After header is documented, and no idempotency key is accepted on the v3 API's write operations, payments included (7 of 15). The docs say production is backed by SLAs, but no SLA document was found and the General Terms of Service supply the service as is (0). The v3 API is generally available. The MCP server is beta (9 of 10).",
          "schema": "Two public OpenAPI 3.0.1 files, `bill-v3-api.json` with 314 operations and `connect-events-api.json` with 12 (25). llms.txt, a Markdown copy of every page and a docs MCP server (10). Every operation has a summary and a description, with a median of 209 characters, links to the guide and notes such as the MFA requirement on payments. Few say when not to call an endpoint (14 of 20). 110 enums, 499 required lists, 271 formats, 82 length limits and 32 patterns. The spec declares no security schemes, so credentials appear as header parameters, and `filters` is a string with its own syntax (11 of 15). 1,025 examples. Errors are documented as one `4XX` and one `5XX` array on 311 operations, with 12 common codes explained and over 500 left to the v2 `Errors.json` call (10 of 15). The path is versioned v3 and the changelog is dated with an RSS feed. Its latest entry is 21 May 2026, and the MCP server, whose guide was updated on 6 October, has no entry (13 of 15).",
          "security": "The AP and AR API signs in with a user's username and password plus a developer key, sent in the request body, and the session carries that user's role with no scopes. The Spend \u0026 Expense API takes a token an ADMIN user generates, with no scopes documented. Sync tokens for app partners can't make payments. The MCP server uses OAuth with PKCE (S256) and a revocation endpoint, with only `openid` and `offline_access` as scopes. No secret travels in a URL (16 of 30). Creating a payment, adding a funding bank account and enabling vendor auto-pay need a session trusted by multi-factor authentication, user roles limit who can pay, bill approval policies are in the API, and the MCP server is read-only. No confirmation step was found for other writes, such as creating a vendor card (16 of 20). Bill and invoice text, vendor names and memos are untrusted content, and no prompt-injection guidance was found (3 of 15). An audit trail endpoint covers vendor creates and edits with the user and source, and users can review and disconnect MCP connections under Connected apps. No audit endpoint for other objects or for API calls was found (7 of 15). Annual SOC 1 and SOC 2 Type II audits and a vulnerability disclosure programme on HackerOne. No bounty is stated and security.txt returns 404 (14 of 20).",
          "transparency": "Closed service with terms at stable URLs, the Developer Terms (effective 3 March 2026) and the General Terms of Service (last updated 10 February 2025) (15 of 30). The Privacy Notice (effective 30 January 2026) covers the products and describes retention by criteria without fixed periods. No data processing agreement was found on the legal index, and no statement on training models with customer data was found in the notice (12 of 30). The Developer Terms commit BILL to commercially reasonable efforts at 30 days' notice of deprecations and breaking changes, and the same document keeps the right to change or discontinue the API at any time. The MFA phone change of 3 April 2026 was announced on 6 February, and the FAQ says there are no plans to deprecate v2 (14 of 20). No sub-processor list or data location statement was found. The legal index has a bank partners page (3 of 20)."
        },
        "sources": [
          {
            "what": "docs index for agents",
            "url": "https://developer.bill.com/llms.txt",
            "seen": "2026-10-08"
          },
          {
            "what": "OpenAPI index",
            "url": "https://developer.bill.com/openapi",
            "seen": "2026-10-08"
          },
          {
            "what": "v3 API OpenAPI file, 314 operations",
            "url": "https://developer.bill.com/openapi/bill-v3-api.json",
            "seen": "2026-10-08"
          },
          {
            "what": "webhooks OpenAPI file, 12 operations",
            "url": "https://developer.bill.com/openapi/connect-events-api.json",
            "seen": "2026-10-08"
          },
          {
            "what": "BILL MCP server guide",
            "url": "https://developer.bill.com/docs/bill-mcp-server.md",
            "seen": "2026-10-08"
          },
          {
            "what": "docs MCP server and llms.txt guide",
            "url": "https://developer.bill.com/docs/ai-agent-resources.md",
            "seen": "2026-10-08"
          },
          {
            "what": "MCP protected resource metadata",
            "url": "https://auth.bill.com/oauth/.well-known/oauth-protected-resource",
            "seen": "2026-10-08"
          },
          {
            "what": "MCP authorisation server metadata",
            "url": "https://auth.bill.com/oauth/.well-known/oauth-authorization-server",
            "seen": "2026-10-08"
          },
          {
            "what": "rate limits",
            "url": "https://developer.bill.com/docs/api-rate-limits.md",
            "seen": "2026-10-08"
          },
          {
            "what": "keys and tokens",
            "url": "https://developer.bill.com/docs/bill-keys-tokens.md",
            "seen": "2026-10-08"
          },
          {
            "what": "Spend \u0026 Expense token guide",
            "url": "https://developer.bill.com/docs/authentication-with-api-token.md",
            "seen": "2026-10-08"
          },
          {
            "what": "common error codes",
            "url": "https://developer.bill.com/docs/common-api-error-codes.md",
            "seen": "2026-10-08"
          },
          {
            "what": "filtering, sorting and pagination",
            "url": "https://developer.bill.com/docs/search-op-with-lists.md",
            "seen": "2026-10-08"
          },
          {
            "what": "sandbox and production differences",
            "url": "https://developer.bill.com/docs/environmental-differences.md",
            "seen": "2026-10-08"
          },
          {
            "what": "sandbox sign-up",
            "url": "https://developer.bill.com/docs/api-sandbox-sign-up.md",
            "seen": "2026-10-08"
          },
          {
            "what": "production go-live guide",
            "url": "https://developer.bill.com/docs/get-started-in-production.md",
            "seen": "2026-10-08"
          },
          {
            "what": "webhook general rules",
            "url": "https://developer.bill.com/docs/bill-webhook-api-general-rules.md",
            "seen": "2026-10-08"
          },
          {
            "what": "webhook notification rules",
            "url": "https://developer.bill.com/docs/bill-webhook-api-notification-rules.md",
            "seen": "2026-10-08"
          },
          {
            "what": "vendor audit trail guide",
            "url": "https://developer.bill.com/docs/getting-audit-trail-details.md",
            "seen": "2026-10-08"
          },
          {
            "what": "FAQ",
            "url": "https://developer.bill.com/docs/faq.md",
            "seen": "2026-10-08"
          },
          {
            "what": "changelog feed",
            "url": "https://developer.bill.com/changelog.rss",
            "seen": "2026-10-08"
          },
          {
            "what": "MFA API change entry, 3 April 2026",
            "url": "https://developer.bill.com/changelog/2026-04-03-mfa-api-improvements.md",
            "seen": "2026-10-08"
          },
          {
            "what": "BILL Developer Terms",
            "url": "https://developer.bill.com/docs/bill-developer-terms.md",
            "seen": "2026-10-08"
          },
          {
            "what": "pricing",
            "url": "https://www.bill.com/product/pricing",
            "seen": "2026-10-08"
          },
          {
            "what": "General Terms of Service",
            "url": "https://www.bill.com/legal/terms-of-service",
            "seen": "2026-10-08"
          },
          {
            "what": "Privacy Notice",
            "url": "https://www.bill.com/privacy",
            "seen": "2026-10-08"
          },
          {
            "what": "security page",
            "url": "https://www.bill.com/security",
            "seen": "2026-10-08"
          },
          {
            "what": "status page incident feed",
            "url": "https://www.billcomstatus.com/api/v2/incidents.json",
            "seen": "2026-10-08"
          },
          {
            "what": "status page components",
            "url": "https://www.billcomstatus.com/api/v2/summary.json",
            "seen": "2026-10-08"
          },
          {
            "what": "security.txt, 404",
            "url": "https://www.bill.com/.well-known/security.txt",
            "seen": "2026-10-08"
          },
          {
            "what": "official MCP registry search",
            "url": "https://registry.modelcontextprotocol.io/v0/servers?search=bill.com",
            "seen": "2026-10-08"
          },
          {
            "what": "RDAP for bill.com",
            "url": "https://rdap.verisign.com/com/v1/domain/bill.com",
            "seen": "2026-10-08"
          }
        ],
        "openQuestions": [
          "unchecked: the live MCP server's tool list, input schemas and readOnlyHint and destructiveHint annotations, which need a signed-in BILL account",
          "unchecked: whether the production 30-day trial needs a payment card, and the per-transaction payment fees, which weren't on the pricing page we read",
          "unchecked: the SLA the docs say backs production. No SLA document was found on the developer site or the legal index",
          "unchecked: the HTTP status code and headers sent with `BDC_1144` and `BDC_1322`, and whether a Retry-After header is returned",
          "unchecked: the help centre article on generating a Spend \u0026 Expense API token, so whether that token can be limited or rotated isn't established",
          "unchecked: the HackerOne programme page, which is drawn by script, so its scope and whether it pays bounties weren't read",
          "unchecked: API changes after 21 May 2026. The docs platform's metadata shows the v3 spec updated on 5 October 2026, with no changelog entry to say what changed",
          "status.bill.com and trust.bill.com didn't answer from our network. The status page is at www.billcomstatus.com",
          "The lead named the REST API and Elements. BILL also runs a beta MCP server, and the party to the Developer Terms is Bill.com, LLC, a subsidiary of BILL Holdings, Inc.",
          "The General Terms of Service bar automated tools that scrape pages of the website. The clause doesn't name the API, so it is recorded here and not as a weakness"
        ]
      },
      "negative": 0,
      "verdict": "A public OpenAPI 3.0.1 spec covers 326 operations, a self-serve sandbox moves no money, and payments need a session trusted by multi-factor authentication. The AP and AR API signs in with a user's password and has no scopes, no idempotency key protects payment calls, and no official SDK was found.",
      "bestFor": "A US company already on BILL that wants an agent to create and read bills, run approvals, schedule vendor payments, raise invoices and manage budgets, vendor cards, card transactions and reimbursements.",
      "strengths": [
        "Two public OpenAPI 3.0.1 files cover 326 operations, with llms.txt, a Markdown copy of every docs page and a docs MCP server at `https://developer.bill.com/mcp`",
        "Creating a payment, adding a funding bank account and enabling vendor auto-pay need an API session trusted by multi-factor authentication",
        "The sandbox is self-serve through a sign-up form, charges no subscription fee and moves no real money",
        "www.billcomstatus.com lists an API Servers component and shows no incident after 15 April 2026",
        "The Developer Terms commit BILL to commercially reasonable efforts at 30 days' notice of deprecations and breaking changes"
      ],
      "weaknesses": [
        "`POST /v3/login` takes a user's username and password with a developer key, and the session carries that user's role with no scopes",
        "No idempotency key is accepted on the 203 write operations of the v3 API, payments included. `X-Idempotent-Key` exists only on two webhook subscription calls",
        "The MCP server is beta, read-only and limited to US organisations, and MCP clients other than Claude and ChatGPT need BILL's approval by email",
        "The changelog's latest entry is dated 21 May 2026, and the MCP server has no entry there",
        "No official SDK, sub-processor list, data processing agreement or security.txt was found, and the audit trail endpoint covers vendors only"
      ],
      "agentNotes": [
        "Sign in with `POST /v3/login` and send `sessionId` and `devKey` as headers on every AP and AR call. The session expires after 35 minutes idle",
        "Send the `apiToken` header alone on `/v3/spend/` paths. Spend \u0026 Expense calls need no login and are limited to 60 a minute per token",
        "Complete the MFA challenge before `POST /v3/payments`. An untrusted session fails with `BDC_1361`",
        "Read back payments before retrying a failed `POST /v3/payments`. No idempotency key is accepted, so a blind retry can pay twice",
        "Keep to three concurrent requests per developer key per organisation and 20,000 an hour. After `BDC_1144`, wait for the next hour"
      ],
      "metrics": {
        "kind": "remote",
        "measured": false
      },
      "reviewCount": 0,
      "avgRating": 0,
      "history": [
        {
          "basis": "public evidence",
          "confidence": "medium",
          "grade": "C",
          "methodology": "0.4",
          "pending": [
            "performance",
            "tasks"
          ],
          "run": "2026-10-01",
          "runLabel": "October 2026 research run",
          "score": 60.9
        }
      ],
      "editorialScores": {
        "ergonomics": 60,
        "maintenance": 32,
        "payments": 25,
        "reliability": 81,
        "schema": 83,
        "security": 56,
        "transparency": 44
      },
      "provenanceScore": 88
    },
    "connect": {
      "http": "curl --request POST \\\n--url 'https://gateway.stage.bill.com/connect/v3/login' \\\n--header 'content-type: application/json' \\\n--data '{\n  \"username\": \"{username}\", \n  \"password\": \"{password}\",\n  \"organizationId\": \"{organization_id}\", \n  \"devKey\": \"{developer_key}\"\n}'"
    },
    "letme": {
      "capability": "https://letme.dev/spend.transactions",
      "tool": "https://letme.dev/bill"
    },
    "notable": [
      "The v3 API is described by two OpenAPI 3.0.1 files, `bill-v3-api.json` with 314 operations and `connect-events-api.json` with 12 for webhooks (https://developer.bill.com/openapi)",
      "52 operations sit under `/v3/spend/` for budgets, vendor cards, transactions, receipts, reimbursements, custom fields and users, the former Divvy product (https://developer.bill.com/openapi/bill-v3-api.json)",
      "The BILL MCP server is in beta at https://gateway.prod.bill.com/ai-mcp-server/v1, read-only over bills, payments, invoices and card transactions, for US organisations (https://developer.bill.com/docs/bill-mcp-server)",
      "MCP clients other than Claude and ChatGPT need approval, requested by email with the URL of the client's identity document (https://developer.bill.com/docs/bill-mcp-server)",
      "Limits are 20,000 requests an hour per developer key, three concurrent requests per key per organisation, 200 logins an hour and 60 Spend \u0026 Expense calls a minute per token (https://developer.bill.com/docs/api-rate-limits)",
      "Creating a payment needs an API session trusted by multi-factor authentication, and a mass payment request can cover up to 2,000 bills (https://developer.bill.com/reference/createpayment)",
      "`GET /v3/spend/cards/{cardId}/pan-jwt` returns a five-minute token that decodes to a vendor card's number, CVV and expiry date (https://developer.bill.com/reference/getpanjwt)",
      "The Developer Terms, effective 3 March 2026, commit BILL to commercially reasonable efforts at 30 days' notice of deprecations and breaking changes (https://developer.bill.com/docs/bill-developer-terms)"
    ],
    "area": "domain-data",
    "details": [
      {
        "label": "API",
        "value": "BILL v3 REST API at https://gateway.prod.bill.com/connect (sandbox https://gateway.stage.bill.com/connect). 314 operations in `bill-v3-api.json`, 203 of them writes, across AP, AR, BILL Network, organisation, partner and Spend \u0026 Expense"
      },
      {
        "label": "Webhooks API",
        "value": "12 operations at https://gateway.prod.bill.com/connect-events. Notifications are signed with HMAC-SHA256 in `x-bill-sha-signature`, time out after 10 seconds and are tried five times. Up to 10 subscriptions per organisation"
      },
      {
        "label": "MCP server",
        "value": "Beta, read-only, at https://gateway.prod.bill.com/ai-mcp-server/v1 (sandbox https://gateway.stage.bill.com/ai-mcp-server/v1). OAuth through auth.bill.com with PKCE. One US organisation per connection. The tool list isn't published"
      },
      {
        "label": "Docs for agents",
        "value": "llms.txt, a Markdown copy of each page at the page URL plus `.md`, and a docs MCP server at https://developer.bill.com/mcp"
      },
      {
        "label": "Credentials",
        "value": "AP and AR, `sessionId` and `devKey` headers after `POST /v3/login` with username and password. Spend \u0026 Expense, `apiToken` header. Partners, `appKey` after `POST /v3/partner/login`. Sync tokens for app partners, with no payment access"
      },
      {
        "label": "Rate limits",
        "value": "20,000 requests an hour per developer key, three concurrent per key per organisation, 200 logins an hour, five text messages a minute, and 60 Spend \u0026 Expense calls a minute per token"
      },
      {
        "label": "Pagination",
        "value": "`max` up to 100 on AP and AR lists and up to 50 on Spend \u0026 Expense lists (default 20), with `nextPage` and `prevPage` cursors, `filters` with nine operators and `sort`"
      },
      {
        "label": "Errors",
        "value": "A JSON array of objects with `timestamp`, `code` (BDC_ prefix), `severity`, `category` and `message`. BILL says there are over 500 codes, listed by the v2 `Errors.json` call"
      },
      {
        "label": "Idempotency",
        "value": "`X-Idempotent-Key` on creating a webhook subscription and a security key only. None on the v3 API's write operations"
      },
      {
        "label": "Sandbox",
        "value": "Self-serve sign-up form, no subscription fee, no real money movement, no accounting system connections. BILL says it deploys there at least twice a day with no SLA"
      },
      {
        "label": "Audit",
        "value": "`GET /v3/reports/audit-trail/vendor/{vendorId}` lists create and edit records for a vendor with the user and source. No audit endpoint for other objects was found"
      },
      {
        "label": "Certifications",
        "value": "Annual SOC 1 and SOC 2 Type II audits per bill.com/security, card payments through a PCI certified vendor, and a vulnerability disclosure programme on HackerOne"
      },
      {
        "label": "Status",
        "value": "www.billcomstatus.com on Statuspage, 15 components including API Servers, Virtual Card and Multi-Factor Authentication"
      },
      {
        "label": "Elements",
        "value": "BILL Elements are embeddable UI widgets for onboarding, MFA and AP payments, for partners building BILL into their own application"
      }
    ],
    "unitPrices": [
      {
        "item": "Spend \u0026 Expense",
        "unit": "seat-month",
        "usd": 0,
        "note": "API access listed. Needs an approved credit application"
      },
      {
        "item": "AP and AR Essentials",
        "unit": "seat-month",
        "usd": 49,
        "note": "API access listed. Per-transaction payment fees apply"
      },
      {
        "item": "AP and AR Team",
        "unit": "seat-month",
        "usd": 65,
        "note": "API access listed"
      },
      {
        "item": "AP and AR Corporate",
        "unit": "seat-month",
        "usd": 89,
        "note": "Enterprise is priced on request"
      }
    ],
    "provenance": {
      "legalEntity": "Bill.com, LLC",
      "domain": "bill.com",
      "domainRegistered": "1994-11-03",
      "endpointOnVendorDomain": true,
      "terms": "https://developer.bill.com/docs/bill-developer-terms",
      "privacy": "https://www.bill.com/privacy",
      "statusPage": "https://www.billcomstatus.com",
      "changelog": "https://developer.bill.com/changelog",
      "securityTxt": "none",
      "checked": "2026-10-08",
      "notes": [
        "The Developer Terms (effective 3 March 2026) are between the developer and Bill.com, LLC and its affiliates, and are accepted when a developer key is generated. The parent company named in the privacy notice is BILL Holdings, Inc.",
        "The BILL Privacy Notice (effective 30 January 2026) names BILL Holdings, Inc. and its subsidiaries Bill.com, LLC, DivvyPay, LLC and Invoice2go, LLC, of San Jose, California.",
        "The API answers at gateway.prod.bill.com and gateway.stage.bill.com, and OAuth for the MCP server at auth.bill.com. The docs send card number decoding to api.divvy.co, a second domain of the vendor's.",
        "The status page is on a separate domain, www.billcomstatus.com, linked from the developer docs. status.bill.com and trust.bill.com didn't answer.",
        "www.bill.com/.well-known/security.txt and www.bill.com/security.txt return 404. The security page sends reports to a HackerOne vulnerability disclosure programme.",
        "The BILL General Terms of Service (last updated 10 February 2025) and separate Spend \u0026 Expense terms govern a customer's account. No data processing agreement or sub-processor list was found on the legal index.",
        "RDAP for bill.com gives a registration date of 1994-11-03 and GoDaddy Corporate Domains, LLC as registrar."
      ],
      "score": 88,
      "checks": [
        {
          "check": "Legal entity named",
          "value": "Bill.com, LLC",
          "points": 20,
          "max": 20,
          "state": "ok"
        },
        {
          "check": "Domain age",
          "value": "bill.com, registered 1994-11-03 (31 years)",
          "points": 15,
          "max": 15,
          "state": "ok"
        },
        {
          "check": "Endpoint on the vendor's domain",
          "value": "gateway.prod.bill.com",
          "points": 15,
          "max": 15,
          "state": "ok"
        },
        {
          "check": "Terms of service",
          "value": "read, states 6 of the 7 things a reader expects",
          "points": 9.1,
          "max": 10,
          "state": "part"
        },
        {
          "check": "Privacy policy",
          "value": "read, states 7 of the 8 things a reader expects",
          "points": 9.3,
          "max": 10,
          "state": "part"
        },
        {
          "check": "Status page",
          "value": "www.billcomstatus.com",
          "points": 10,
          "max": 10,
          "state": "ok"
        },
        {
          "check": "Changelog",
          "value": "published",
          "points": 10,
          "max": 10,
          "state": "ok"
        },
        {
          "check": "security.txt",
          "value": "not found",
          "points": 0,
          "max": 10,
          "state": "no"
        }
      ],
      "policies": [
        {
          "kind": "terms",
          "url": "https://developer.bill.com/docs/bill-developer-terms",
          "state": "read",
          "readAt": "2026-10-08",
          "statedDate": "2026-03-03",
          "words": 7752,
          "points": 9.1,
          "max": 10,
          "expected": [
            {
              "key": "terms.date",
              "label": "Gives the date it was last updated",
              "found": true,
              "quote": "Effective date: March 3, 2026",
              "says": "Last updated 2026-03-03"
            },
            {
              "key": "terms.law",
              "label": "Names the governing law or courts",
              "found": true,
              "quote": "This Agreement will be governed by and interpreted in accordance with the internal laws of the state of California.",
              "says": "The law of the State of California"
            },
            {
              "key": "terms.liability",
              "label": "States a limit on its liability",
              "found": true,
              "quote": "SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES, AND SO PARTS OF THE ABOVE LIMITATION MAY NOT APPLY TO YOU.",
              "says": "Rules out indirect and consequential losses, with no cap named in this sentence"
            },
            {
              "key": "terms.termination",
              "label": "Says how the agreement or account can be ended",
              "found": true,
              "quote": "BILL reserves the right to establish and enforce rate limits on the BILL API at its sole discretion, and may temporarily suspend or throttle your access without notice if your usage significantly exceeds typical patterns or risks degrading platform performance."
            },
            {
              "key": "terms.changes",
              "label": "Says how changes to the terms are announced",
              "found": true,
              "quote": "BILL may modify this Agreement from time to time by posting the modified Agreement to its developer web site.",
              "says": "Changes are posted, with no other notice named"
            },
            {
              "key": "terms.use",
              "label": "Lists what users may not do",
              "found": true,
              "quote": "You may not: (1) use the Developer Materials, BILL API, or Test Account to design or develop anything other than an Integrated Application (2) make any more copies of the Developer Materials than are reasonably necessary for the authorized use and backup and archival purposes;"
            },
            {
              "key": "terms.sla",
              "label": "Refers to a service level or uptime commitment",
              "found": false
            }
          ],
          "toKnow": [
            {
              "key": "terms.cutoff",
              "label": "Says access can be ended without notice or for any reason",
              "found": true,
              "quote": "BILL reserves the right to establish and enforce rate limits on the BILL API at its sole discretion, and may temporarily suspend or throttle your access without notice if your usage significantly exceeds typical patterns or risks degrading platform performance."
            }
          ],
          "notes": [
            {
              "date": "2026-10-08",
              "text": "Customer Data may be sent to third-party AI models or applications over secure protocols such as MCP, solely to support authorised use of the Services, subject to conditions the clause lists.",
              "quote": "you may transmit Customer Data via secure protocols (such as MCPs) to third-party artificial intelligence models or applications solely to facilitate your authorized use of the Services"
            },
            {
              "date": "2026-10-08",
              "text": "The organisation is responsible for all transactions made through its account or login credentials, including unauthorised or fraudulent ones.",
              "quote": "You will be responsible for all transactions that result from such access, even if they are unauthorized, fraudulent, or you did not want the transactions performed."
            },
            {
              "date": "2026-10-08",
              "text": "After the first year the agreement renews automatically for successive one-year terms, subject to payment of any annual renewal fees.",
              "quote": "Thereafter, subject to Your payment of annual renewal fees (if any specified by BILL) and compliance with the terms of this Agreement, the term of this Agreement will automatically renew for successive one (1) year terms, unless sooner terminated as set forth herein."
            }
          ]
        },
        {
          "kind": "privacy",
          "url": "https://www.bill.com/privacy",
          "state": "read",
          "readAt": "2026-10-08",
          "statedDate": "2026-01-30",
          "words": 6381,
          "points": 9.3,
          "max": 10,
          "expected": [
            {
              "key": "privacy.date",
              "label": "Gives the date it was last updated",
              "found": true,
              "quote": "Effective date: January 30, 2026",
              "says": "Last updated 2026-01-30"
            },
            {
              "key": "privacy.collected",
              "label": "Says what personal data is collected",
              "found": true,
              "quote": "Information We Collect and the Sources From Which We Collect it"
            },
            {
              "key": "privacy.retention",
              "label": "Says how long data is kept",
              "found": true,
              "quote": "We will retain Your information as long as it is necessary to comply with Our internal records retention and management policies and procedures and to provide You with the Services or administer Your account, or as long as necessary to comply with legal obligations, resolve disputes, reserve legal rights, and enforce…",
              "says": "For as long as needed, with no period named"
            },
            {
              "key": "privacy.processors",
              "label": "Says who else receives the data",
              "found": true,
              "quote": "When You share information with Us, or bring over information from third parties (like a bank or accounting software provider), We use that data together, not just within the individual offering(s) You’re using, such as Bill Payments, Account Receivables, Consoles, Card Disbursements, Spend and Expense, and Financial…"
            },
            {
              "key": "privacy.sale",
              "label": "Says whether personal data is sold or shared for advertising",
              "found": true,
              "quote": "The BILL Companies will not sell, lease, rent, or trade Your personal information to any third party for that party’s marketing or promotional purposes, unless You give Your consent.",
              "says": "Says it does not sell personal data"
            },
            {
              "key": "privacy.rights",
              "label": "Says what rights people have over their data",
              "found": false
            },
            {
              "key": "privacy.contact",
              "label": "Gives a privacy contact",
              "found": true,
              "quote": "…unable to log in, please click on the chat modal here to connect with Us) or Our Privacy Team at privacy@hq.bill.com or contact us at:",
              "says": "privacy@hq.bill.com"
            },
            {
              "key": "privacy.transfers",
              "label": "Says where data is transferred or stored",
              "found": true,
              "quote": "For example, if You are located in the European Economic Area (“EEA”), Canada, New Zealand, or Australia, We may transfer Your personal information to the United States or other countries outside of the country of Your residence.",
              "says": "Data goes to the United States"
            }
          ],
          "notes": [
            {
              "date": "2026-10-08",
              "text": "The notice states that it does not apply to business information the customer supplies.",
              "quote": "This Privacy Notice does not apply to business information You might provide."
            },
            {
              "date": "2026-10-08",
              "text": "Information about the customer may be used for marketing by BILL and by banks that sell services through BILL, including to identify similar prospective customers.",
              "quote": "We may also use information about You for Our (and banks that offer services through BILL) marketing purposes, including to identify other similar prospective customers who may be interested in the Services."
            }
          ]
        }
      ]
    },
    "pageJsonUrl": "https://www.anchorterminal.com/tools/bill.json",
    "live": {
      "slug": "bill",
      "probe": {
        "target": "https://gateway.prod.bill.com/connect",
        "method": "get",
        "lastAt": "2026-10-08T21:12:05.582437227Z",
        "lastOk": true,
        "lastStatus": 403,
        "lastMs": 464,
        "lastNote": "asks for credentials",
        "authRequired": true,
        "uptime24h": 100,
        "uptime30d": 100,
        "p50ms24h": 440,
        "p95ms24h": 521,
        "samples24h": 21,
        "samples30d": 21,
        "days": [
          {
            "date": "2026-10-08",
            "probes": 21,
            "ok": 21
          }
        ]
      },
      "vendorStatus": {
        "page": "https://www.billcomstatus.com",
        "indicator": "none",
        "summary": "All Systems Operational",
        "checkedAt": "2026-10-08T21:05:52.445436869Z"
      },
      "updatedAt": "2026-10-08T21:12:05.582437227Z"
    }
  }
}
