# ScanPay Session Deposit

> ScanPay Session Deposit is a paid API for AI agents from scanpay-ob3w.onrender.com, paid per call via x402, $0.85/call, status unknown (last checked 2026-10-31).

Registers a completed Solana deposit transaction to create an authenticated session with credits for code security scanning

## Facts

- Endpoint: POST https://scanpay-ob3w.onrender.com/api/v1/session/deposit?utm_source=zero.xyz
- Price: $0.85/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-31
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/scanpay-session-deposit-8b379113
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_Ftk6ohTnHx5K9mNzQj8lx

Status and success rate cover calls made through Zero and Zero's own probes. Third-party monitors may report differently.

## How to call it through Zero

Zero handles the 402 payment challenge and records the run. With the Zero CLI installed (`npm i -g @zeroxyz/cli`):

```sh
zero fetch --capability scanpay-session-deposit-8b379113 -d '<json body>'
```

Example prompt: I just sent 0.85 USDC on Solana to deposit into ScanPay — here's my transaction signature: 5Kj8mNqPx... — can you submit that to register my session and get me my scan credits?

## When to prefer this

Use this endpoint immediately after completing a Solana USDC payment to ScanPay to convert that on-chain transaction into an active scanning session. This is the required first step before calling any code analysis endpoints — without a valid session ID from this deposit registration, scan calls will be rejected.

## Known failure modes

- Invalid or unrecognized transaction signature returns an error or zero credits
- Transaction not yet confirmed on-chain results in deposit not recognized
- Duplicate submission of the same transaction hash may fail or return existing session
- Expired or revoked transaction hash not accepted
- Missing deposit_tx field returns 400 validation error

## How this service works

Deterministic AST code security scanner with x402 Solana micropayments, remote MCP, and ERC-8183 Evaluator oracle.

## Output

Returns a session object containing a unique session_id for subsequent scan API calls, the number of credits_remaining available for scans, and an expires_at ISO timestamp indicating when the session becomes invalid.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "required": [
  "deposit_tx"
 ],
 "properties": {
  "deposit_tx": {
   "type": "string",
   "description": "Signature or transaction hash of the deposit payment"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "expires_at": "2026-12-31T00:00:00Z",
  "session_id": "sess_abc123",
  "credits_remaining": 10
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/scanpay-session-deposit-8b379113/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from scanpay-ob3w.onrender.com](https://www.zero.xyz/host/scanpay-ob3w.onrender.com/llms.txt)