Mainnet-first automation starter for Tempo Machine Payment Protocol workflows.

This repository is designed for controlled, budget-limited MPP activity on Tempo mainnet, with workflow orchestration, randomized daily execution, provider safety controls, retry logic, and quota-aware circuit breakers.

• This project is for real mainnet execution
• Every live MPP action can spend real funds
• Rewards, eligibility, snapshots, and any future incentive logic remain unknown
• Some providers are intentionally excluded from autopilot because they are higher risk or technically unstable
• You should use a dedicated automation account or delegated access key, not your primary wallet secrets

For this repository, the recommended default path is the official Tempo account flow via wallet.tempo.xyz, followed by an access-key setup for automation.

• Use the official Tempo account as explicit profile main
• Use a delegated access key for automated execution
• Do not treat Rabby or MetaMask as the default setup path for this repo
• Tempo may support multiple account paths in general, but this project is documented around the wallet.tempo.xyz / passkey / access-key workflow

Official Tempo docs for account setup:

• https://docs.tempo.xyz/guide/use-accounts/embed-passkeys
• https://docs.tempo.xyz/guide/use-accounts/connect-to-wallets

AI setup prompt for this exact wallet.tempo.xyz -> Access Key -> .env flow:

• ACCESS_KEY_SETUP.md

This repository is primarily about MPP automation, but a few manual Tempo mainnet actions fit well alongside it.

• .tempo domain purchase can be a useful manual companion action
• for this repo's documented mainnet path, the recommended purchase flow is the official wallet.tempo.xyz account path
• do not treat Rabby or MetaMask as the reference purchase path for the documented flow here
• if you want to buy a domain through InfinityName, you can use this referral link:
  • https://infinityname.com?ref=0x62ecabc2a9e3987a96cb977fea7fc05c003f70bf
• after purchase, you can optionally set that domain as your primary domain in a separate manual follow-up

Practical example from the maintained mainnet setup behind this repo:

• domain purchased: efidal.tempo
• wallet path used: https://wallet.tempo.xyz/
• purchase surface: https://infinityname.com/

• runs a mainnet-only Tempo MPP agent
• supports randomized workflow execution inside a daily budget cap
• combines research, email, shopping, travel, and creative provider tasks
• blocks quota-failing providers for the rest of the day
• trims daily plans automatically when estimated spend would exceed the configured cap

• Exa: exa_search, exa_contents, exa_answer
• Parallel: parallel_search, parallel_extract
• Perplexity: perplexity_embed, perplexity_search
• Fal: fal_flux_schnell
• StableEmail: stableemail_send
• StableTravel: stabletravel_flights
• StableEnrich: stableenrich_search

Manual-only:

• openai_embeddings

Currently blocked:

• browserbase_search
• browserbase_fetch

1. Copy .env.example to .env.
2. Configure your official Tempo account as profile main.
3. Add a delegated access key if you want automated mainnet execution.
4. Set optional safety values such as:
   • TEMPO_AGENT_DAILY_MAX_SPEND_USDC
   • TEMPO_AGENT_MPP_MAX_CHARGE
   • TEMPO_MPP_EMAIL_TO
5. Inspect the agent state:

python scripts/tempo_agent.py status

6. Run a single manual MPP action:

python scripts/tempo_agent.py run-now --kind mpp --category research --service exa_search

7. Start the randomized loop:

.\scripts\start_tempo_agent_mpp_random_full.ps1

8. Stop the loop:

python scripts/tempo_agent.py stop

• ACCESS_KEY_SETUP.md
  • copy-paste AI prompt for the official Tempo account and delegated access-key setup flow
• TEMPO_AGENT.md
  • operating guide, environment options, commands, provider behavior
• playbook.md
  • provider catalog, capability matrix, live autopilot model

• scripts
  • core agent, provider runner, profile helpers, and start scripts
• TEMPO_AGENT.md
  • operator-facing documentation
• playbook.md
  • workflow and provider reference
• .env.example
  • public-safe configuration template

• Never commit your real .env
• Never publish private keys, access keys, real email addresses, state files, logs, or CSV histories
• Treat all spend caps as safety rails, not guarantees
• Test with read-only quoting commands before enabling live execution

Read-only example:

node scripts/tempo_mpp.mjs quote --service-name exa_answer

This repository focuses on operational MPP automation, not on claiming rewards or promising incentive outcomes.