---
title: "Pricing: pilot, team and assurance engagements | Settlens"
description: "How Settlens pricing works: a scoped pilot, Team access for CI and monitoring, or periodic independent assurance, quoted on endpoints, facilitators and cadence."
url: https://settlens.com/pricing
last_updated: 2026-10-13
---

# Pricing scoped to your endpoints and facilitators

> **In short:** Settlens has no public price list. Each engagement (a one-off Pilot, Team access for your own CI and monitoring, or periodic independent Assurance) is quoted in writing after a call, from the endpoints and facilitators in scope and the cadence. The browser tools and the offline tools of settlens.com/mcp are free.

Settlens is offered as engagements, not seats. Each one is quoted after a short call, based on how many paid endpoints and facilitators are in scope and how often they need checking.

[Request a pilot](https://settlens.com/contact) [How pricing works](https://settlens.com/pricing#how-pricing-works)

The [browser tools](https://settlens.com/tools) and the offline tools of the [remote MCP endpoint](https://settlens.com/pricing#free-mcp-tools) are free to use.

## Three ways to work with Settlens

Start with a pilot, then keep the checks running yourself, have them repeated independently, or both.

- **Pilot**

  Start here

  One-off quoted per scope

  A scoped assessment of your x402 endpoints, run by Settlens, with a written report and signed evidence.

  [Request a pilot](https://settlens.com/contact)
  - Passive scan of each in-scope paid endpoint: 402 handshake, PAYMENT-REQUIRED, official @x402/core schema, resource binding, drift
  - Facilitator GET /supported scan and coverage of your advertised requirements
  - Optional fail-closed probe: one invalid signature, with the owner's written authorization
  - Offline verification of payment authorizations you capture (EVM exact scheme and Solana)
  - Written report with findings and fixes, plus JSON, HTML and SARIF reports
  - ed25519-signed evidence attestation you can verify offline

  Recommended setup: one endpoint and one facilitator, on a test network or staging.

- **Team**

  Ongoing quoted per scope

  Settlens in your own CI and production monitoring for the x402 endpoints you operate, with the CLI, its local MCP server, the GitHub Action and the container that pilot participants receive.

  [Talk to us](https://settlens.com/contact)
  - CLI for Node.js 20.19 or newer and the pinned non-root container image
  - GitHub composite Action: fail-on threshold, allowed-hosts for custom headers, SARIF for code scanning
  - Monitor: baseline comparison, regression detection, webhook alerts, non-zero exit at your threshold
  - Offline verification of captured payment authorizations (EVM exact scheme and Solana)
  - Local MCP server with all 8 tools, including the passive network scans, for your agents

  Self-run results are your own evidence; they are not an independent assessment.

- **Assurance**

  Periodic quoted per cadence

  Independent periodic assessment of your x402 endpoints, with signed evidence for partners and auditors.

  [Talk to us](https://settlens.com/contact)
  - Assessment repeated at an agreed cadence, by Settlens
  - Comparison with the previous assessment, so regressions stand out
  - A signed attestation for every report, bound to its SHA-256 digest and a timestamp
  - Evidence your partners and auditors verify themselves with verify-report and evidence verify

  Reports describe observed behavior. They are not a certification or legal advice.

## Compare the engagements

Every engagement uses the same check catalog. What changes is who runs the checks, how often, and who signs the evidence.

_Settlens engagement models compared_

| Capability | Pilot | Team | Assurance |
| --- | --- | --- | --- |
| Who runs the checks | Settlens | Your team | Settlens |
| Cadence | Once, on the agreed scope | Every build and every schedule you set | Agreed cadence |
| Passive endpoint scan | Yes | Yes | Yes |
| Facilitator /supported scan | Yes | Yes | Yes |
| Invalid-signature fail-closed probe | With the owner's written authorization | With the owner's written authorization | With the owner's written authorization |
| Offline payment signature verification | Yes | Yes | Yes |
| JSON, HTML and SARIF reports | Yes | Yes | Yes |
| Written report with findings and fixes | Yes | No | Yes |
| Ongoing CI gate and production monitoring | No | Yes | Combine with Team |
| Signed evidence attestation | Signed by Settlens | Signed with your own key | Signed by Settlens |
| Independent of the endpoint operator | Yes | No | Yes |

## How pricing works

There is no public price list yet. Every engagement is quoted after a call, from three inputs.

- **Endpoints in scope**

  The number of x402 paid resources to assess, monitor or gate in CI.

- **Facilitators in scope**

  The facilitators whose /supported capabilities and /verify behavior are checked.

- **Cadence**

  One pilot, continuous use by your team, or independent assessments repeated on a schedule.

## From request to kickoff

Four steps, and nothing is assessed before the scope is agreed in writing.

1. **Send a request**

   Use the [pilot request form](https://settlens.com/contact) or write to [contact@settlens.com](mailto:contact@settlens.com) with the endpoints, facilitators or agent flows you have in mind.

2. **Scoping call**

   We agree on what is in scope, the terms each endpoint should advertise and whether an authorized active probe is wanted.

3. **Written quote and scope**

   You receive the scope, the deliverables and the price in writing. Nothing starts before you accept it.

4. **Authorization and kickoff**

   For an active probe, the endpoint owner's written authorization comes first. Its reference is passed to `--authorization-ref` and recorded in the report. See the [security page](https://settlens.com/security) for how tests are gated.

## Free: the remote MCP offline tools

The MCP endpoint at `https://settlens.com/mcp` lists these tools without any token. They compute on the inputs you send, never pay and never need a key. The [x402 checker](https://settlens.com/tools/x402-checker) runs `evaluate_payment_requirements` in your browser.

_Tools the remote MCP endpoint exposes without a token_

| Tool | What it does |
| --- | --- |
| `evaluate_payment_requirements` | Should I pay this x402 request? |
| `verify_payment_signature` | Verify an exact EVM payment signature |
| `verify_solana_transaction` | Verify Solana signatures and payment instructions |
| `verify_report` | Verify a Settlens report |
| `verify_attestation` | Verify a Settlens evidence attestation |
| `list_checks` | List Settlens checks |

**Add the remote endpoint to Claude Code**

```shell
claude mcp add --transport http settlens https://settlens.com/mcp
```

> **Network tools need a token**
>
> `scan_endpoint` and `scan_facilitator` are passive and run on the remote endpoint only with a Settlens API token. Requests are rate limited per IP address. See the [MCP server page](https://settlens.com/mcp).

## Pricing questions

**Why are there no prices on this page?**

Prices are not public yet. The work depends on how many endpoints and facilitators are in scope and how often they are checked, so each engagement is quoted in writing after a call.

**Is anything free?**

Yes. The offline tools of the remote MCP endpoint, including `evaluate_payment_requirements`, are free to use within the rate limits, from any MCP client or with the [browser tools](https://settlens.com/tools). The [Learn](https://settlens.com/learn) guides and the [documentation](https://settlens.com/docs) are public too.

**Where should we start?**

With a pilot on one endpoint and one facilitator, ideally on a test network or staging. Team and Assurance can follow, separately or together.

**Do you need our wallets, keys or tokens?**

No. Settlens never pays, never signs a payment, never holds your keys or funds and never calls a facilitator's /settle. Passive scans need no credentials at all.

**Can we install Settlens from npm?**

No. Settlens is in a private repository and is not published on npm or as open source. Pilot participants receive the CLI (Node.js 20.19 or newer), the GitHub Action and the container. [Request a pilot](https://settlens.com/contact) to get access.

## Get a quote for your endpoints

Tell us which endpoints, facilitators or agent flows you want checked. We reply by email to set up a short scoping call.

[Request a pilot](https://settlens.com/contact) [Read the FAQ](https://settlens.com/faq)