# Run Nansen API Calls Through Tempo MPP

Paid Nansen API access can require API keys or wallet setup. This skill shows how to use Tempo MPP for pay-per-call requests.

## Install

```bash
npx skillstore add internet-court/nansen-mpp-payment
```

## Metadata

- Status: approved
- Slug: internet-court-nansen-mpp-payment
- Skillstore revision: r1
- Version status: missing
- Tree hash: 4c522159ddd869b35faeae079b1398ab4604f7c286f394b1aa567c064c62cd01
- Author: internet-court
- GitHub username: internet-court
- License: MIT
- Repository: https://github.com/internet-court/internet-court-skill/tree/main/vendored/nansen/nansen-mpp-payment
- Ref: 3f6e026a3363e0954ede7bef0cfe88d4475de137
- Supported tools: Claude, Codex, Claude Code
- Audit status: complete
- Agent install advisory: blocked
- Manual install advisory: allowed\_with\_warning
- Artifact signature: available
- Audit attestation: unavailable
- Human verification: not\_verified
- Risk factors: external\_commands, network, filesystem
- Quality score: 38
- Quality tier: warning
- Public page: https://skillstore.pages.dev/skills/internet-court-nansen-mpp-payment
- Manifest: https://skillstore.pages.dev/api/skills/internet-court-nansen-mpp-payment/manifest

## Capabilities

- Explain when Tempo MPP is the right Nansen access method.
- List one-time Tempo CLI setup steps for wallet login and funding.
- Show paid Nansen API request patterns using tempo request.
- Help discover paid endpoint metadata through the Nansen well-known endpoint.
- Compare MPP headers and wallet handling with x402.

## Use Cases

- Access Nansen Without API Keys: Use Tempo MPP when a paid endpoint supports payment credentials and the user wants no long-lived API key.
- Test MPP Payment Flows: Compare Nansen API key, x402, and MPP paths before building payment-aware API integrations.
- Document Paid Endpoint Discovery: Check Nansen paid resource metadata and explain which payment rails are available for each endpoint.

## Prompt Templates

### Choose an Access Method

```
Explain whether Tempo MPP fits my Nansen task. I do not have a Nansen API key and want to avoid local wallet management.
```

### Prepare Tempo Setup

```
Walk me through preparing Tempo for Nansen MPP access. Include login, funding checks, and approval points before paid requests.
```

### Plan a Paid Request

```
Help me plan a Nansen MPP request for this endpoint: [endpoint]. Include schema lookup, cost awareness, and required approvals.
```

### Review Payment Integration

```
Review this Nansen workflow for API key, x402, and Tempo MPP tradeoffs: [workflow]. Identify payment, credential, and operational risks.
```

## Limitations

- Requires the Tempo CLI to be installed separately.
- Does not manage API keys, wallet keys, or Nansen credentials.
- Can trigger paid API requests when commands are executed.
- Depends on Nansen and Tempo endpoint availability.

## Best Practices

- Confirm user approval before installing Tempo or running billable requests.
- Check endpoint schemas before sending paid requests.
- Use read-only discovery steps before wallet funding or paid calls.

## Anti Patterns

- Do not run remote installer scripts without verifying the source.
- Do not send wallet or payment actions without explicit consent.
- Do not use this skill when an API key or x402 flow is required.

## Security Audit

- Audited at: 2026-07-21T03:36:43.118\+00:00
- Summary: Most external-command detections are false positives caused by Markdown inline-code markers and fenced examples. The skill does instruct users to download and execute a remote Tempo installer through a curl-to-bash pipeline, which is a critical supply-chain execution risk. Direct requests to Nansen endpoints are intentional but make network calls and may incur payment charges through the Tempo wallet.

## Stats

- Views: 0
- Downloads: 5
- Favorites: 1
- Popularity score: 0