---
title: "Contact Settlens and request a pilot"
description: "Request a Settlens pilot for your x402 endpoints, facilitator or agent payments, or email contact@settlens.com. What to send, what not to send, what comes next."
url: https://settlens.com/contact
last_updated: 2026-10-14
---

# Request a pilot or a quote

> **In short:** To request a Settlens pilot or a quote, use the form at settlens.com/contact or write to contact@settlens.com with the x402 endpoints, facilitators or agent flows to check. Never include private keys, tokens or real PAYMENT-SIGNATURE values. A person replies by email to scope the work.

Start with one x402 V2 HTTP endpoint, a facilitator profile or an agent's spending policy. Tell us what could break; we reply by email to agree the scope, authorization and quote.

Prefer email? Write to [contact@settlens.com](mailto:contact@settlens.com).

## Your request

All fields are required. A few lines are enough: we will ask for the details we need.

> **Never send secrets**
>
> Do not include private keys, seed phrases, API or bearer tokens, real PAYMENT-SIGNATURE values or customer data. Scoping a pilot or a quote never needs them, and this form is not a secure channel for them.

- **Email:** [contact@settlens.com](mailto:contact@settlens.com)
- **Languages:** English, French
- **Security reports:** See [responsible disclosure](https://settlens.com/security#disclosure)
- **Publisher:** [Legal notice](https://settlens.com/legal)

## What a first endpoint pilot can deliver

Choose the checks with the integration owner. The written scope and quote determine the work; submitting this form does not start a scan or a paid engagement.

- **[A baseline you can review](https://settlens.com/docs/reports)**

  A passive assessment of the HTTP challenge, resource binding and explicit recipient, asset, network and amount policy, with JSON, HTML and SARIF evidence.

- **[Changes against reviewed terms](https://settlens.com/docs/monitor)**

  If monitoring is in scope, explicitly approve a payment reference and review detected changes and incidents. New observations never approve themselves.

- **[A gate for your next release](https://settlens.com/docs/github-action)**

  Run the agreed checks in CLI/CI and fail on the chosen severity threshold. Validate the behavior with controlled examples before using it in your release process.

## Good reasons to reach out

- **[x402 V2 HTTP API](https://settlens.com/use-cases/api-sellers)**

  You sell API access over x402 V2 and want an outside check of the HTTP 402 challenge, advertised payment terms and resource binding.

- **[Facilitator review](https://settlens.com/use-cases/facilitators)**

  You run a facilitator and want its /supported capabilities checked and proof that /verify rejects an invalid signature.

- **[AI agent payments](https://settlens.com/use-cases/agent-builders)**

  Your agents pay x402 resources and you want a preflight check and a spending policy before any payment is signed.

- **[Partner or auditor evidence](https://settlens.com/product/evidence)**

  You need reports and signed attestations that a partner or auditor can verify offline, without trusting your word.

## What happens next

Every request is read and answered by a person. Here is how a pilot usually starts.

1. **We read your request**

   The reply comes from [contact@settlens.com](mailto:contact@settlens.com), usually with a few questions or a proposal for a short call.

2. **We scope it together**

   Which paid endpoints, facilitators or agent flows are in scope, the payment terms you expect them to advertise (scheme, network, recipient, asset, maximum amount) and whether an active probe is wanted.

3. **You confirm in writing**

   You receive a written scope and quote. If an active probe is in scope, the endpoint owner's written authorization is required; its reference is passed to `--authorization-ref` and recorded in the report. Passive scans need no credentials.

4. **We assess and deliver**

   Passive scans, the optional authorized probe, JSON, HTML and SARIF reports and an ed25519-signed attestation you can verify offline. See [pricing](https://settlens.com/pricing) for the engagement models.

## What to include

- The URLs of the paid resources to assess. Staging or test-network endpoints are ideal.
- The facilitator base URL, if you run one or rely on one.
- The terms you expect each endpoint to advertise, so policy findings are meaningful.
- Who can authorize an active probe, if you want one.

Not sure what to ask for? The [FAQ](https://settlens.com/faq) answers the common questions, and the [quickstart](https://settlens.com/docs/quickstart) shows what a scan looks like.

## Want to see the checks first?

The offline tools of the remote MCP endpoint are free to use: paste a payment request into the browser checker, or point any MCP client at settlens.com/mcp and check a payment request before paying.

[Try the x402 checker](https://settlens.com/tools/x402-checker) [Explore the MCP server](https://settlens.com/mcp)