Add Tempo Data API to First-Party services - #24
Open
compusophy wants to merge 2 commits into
Open
Conversation
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adds a live, MPP-native paid service to the First-Party list.
Tempo Data API — pay-per-call on-chain data plus AI image generation for Tempo mainnet (chain 4217), settled in USDC.e via HTTP 402.
GET /tempo/token?address=0x…— TIP-20 token metadata (name, symbol, decimals, totalSupply) — 0.01 USDC.eGET /tempo/balance?token=0x…&holder=0x…— token balance (raw + formatted) — 0.01 USDC.ePOST /image— AI image generation, ~1024px PNG — 0.10 USDC.ex-payment-infooffers at/openapi.jsonLive now —
curl https://venture-mpp.vercel.app/tempo/token?address=0x20c000000000000000000000b9537d11c60e8b50returns a 402 MPP challenge.