How do I install the Ekx Tempo skill?

Run npx skillmds@latest add ekinoxis-evm/ekx-tempo in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Ekx Tempo safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: makes network calls, reads secrets. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Ekx Tempo?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Ekx Tempo free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Ekx Tempo?

Ekinoxis-evm (@ekinoxis-evm) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Ekx Tempo by ekinoxis-evm — Agent Skill

Name: Ekx Tempo
Rating: 4.2 (5 reviews)
Author: Ekinoxis-evm

Ekx Tempo

The Tempo chain and Machine Payments Protocol (MPP) — the tempo CLI for agent-paid web requests, pathUSDC, the Moderato testnet, sponsored transactions and wallet setup. Use when an agent needs to pay per request without API keys, or when evaluating MPP against x402.

Ekinoxis-evm Updated Sep 22, 2026

File contents

Tempo / MPP

An agent-payments chain, used in our agent-payments work.

Vendored authority: ../../vendor/tempo/, a full docs mirror. Web: https://docs.tempo.xyz

What it does

Lets a Claude Code agent make paid web requests from a Tempo wallet via the Machine Payments Protocol — micropayments per request, no API key, no subscription.

Claude Code agent
  └── tempo request (CLI)
        └── Tempo wallet (pathUSDC)
              └── the paid API

Same problem as x402, different chain and a CLI-first ergonomics. x402 settles on Base in USDC; Tempo settles on Tempo in pathUSDC. We have both in the portfolio because both were being evaluated — neither is production infrastructure yet.

Environment

NEXT_PUBLIC_TEMPO_RPC_URL=            # https://rpc.moderato.tempo.xyz
NEXT_PUBLIC_TEMPO_PATHUSDC_ADDRESS=   # 0x20c0000000000000000000000000000000000000

Endpoints: RPC rpc.moderato.tempo.xyz · sponsor sponsor.moderato.tempo.xyz and sponsor.devnet.tempo.xyz · wallet wallet.tempo.xyz · keys keys.tempo.xyz · explorer explore.tempo.xyz.

pathUSDC also has 6 decimals. Same rule as USDC — see ../ekx-circle-usdc/SKILL.md.

Session check

Run this before trusting anything in a Tempo session:

tempo request --dry-run -X POST \
  --json '{"query":"test"}' \
  https://parallelmpp.dev/api/search

--dry-run prices the request without paying. Use it on every new endpoint before letting an agent loop over it.

Rules

--dry-run first, every new endpoint.
Budget per agent run. Same hazard as x402: an unbounded loop over a paid endpoint drains the wallet quietly.
Moderato is a testnet. Do not treat balances as real, and do not build a product dependency on testnet endpoints.
Keep the agent wallet small. It signs without a human.

---name: ekx-tempodescription: The Tempo chain and Machine Payments Protocol (MPP) — the tempo CLI for agent-paid web requests, pathUSDC, the Moderato testnet, sponsored transactions and wallet setup. Use when an agent needs to pay per request without API keys, or when evaluating MPP against x402.---# Tempo / MPPAn agent-payments chain, used in our agent-payments work.Vendored authority: [`../../vendor/tempo/`](../../vendor/tempo/), a full docs mirror.Web: https://docs.tempo.xyz---## What it doesLets a Claude Code agent make **paid web requests** from a Tempo wallet via theMachine Payments Protocol — micropayments per request, no API key, no subscription.```Claude Code agent └── tempo request (CLI) └── Tempo wallet (pathUSDC) └── the paid API```Same problem as [`x402`](../ekx-x402/SKILL.md), different chain and a CLI-first ergonomics.x402 settles on Base in USDC; Tempo settles on Tempo in pathUSDC. We have both in theportfolio because both were being evaluated — **neither is production infrastructure yet**.---## Environment```bashNEXT_PUBLIC_TEMPO_RPC_URL= # https://rpc.moderato.tempo.xyzNEXT_PUBLIC_TEMPO_PATHUSDC_ADDRESS= # 0x20c0000000000000000000000000000000000000```Endpoints: RPC `rpc.moderato.tempo.xyz` · sponsor `sponsor.moderato.tempo.xyz` and`sponsor.devnet.tempo.xyz` · wallet `wallet.tempo.xyz` · keys `keys.tempo.xyz` ·explorer `explore.tempo.xyz`.**pathUSDC also has 6 decimals.** Same rule as USDC — see [`../ekx-circle-usdc/SKILL.md`](../ekx-circle-usdc/SKILL.md).---## Session checkRun this before trusting anything in a Tempo session:```bashtempo request --dry-run -X POST \ --json '{"query":"test"}' \ https://parallelmpp.dev/api/search````--dry-run` prices the request without paying. Use it on every new endpoint beforeletting an agent loop over it.---## Sponsored transactionsThe sponsor endpoint pays gas so the agent wallet only needs pathUSDC, not a gastoken. That is the main ergonomic win over doing this on Base directly.---## Rules1. **`--dry-run` first**, every new endpoint.2. **Budget per agent run.** Same hazard as x402: an unbounded loop over a paid endpoint drains the wallet quietly.3. **Moderato is a testnet.** Do not treat balances as real, and do not build a product dependency on testnet endpoints.4. **Keep the agent wallet small.** It signs without a human.

Frequently asked questions