Google Maps
Search Google Maps places by text query to retrieve matching place results with details like name, address, and location.
https://googlemaps.mpp.tempo.xyzSearch Google Maps places by text query to retrieve matching place results with details like name, address, and location.
Look up aerial video content for a given location using the Google Maps Aerial View API.
Renders an aerial video of a location using Google Maps Aerial View API.
Generate a static map image for a given location, zoom level, and map type using Google Maps.
Returns travel time and distance between one or more origin and destination pairs using Google Maps.
Convert a street address to coordinates or reverse-geocode lat/lng to a human-readable address using Google Maps.
Compute optimized routes between two or more locations using the Google Maps Routes API v2.
Fetch a 2D map tile image by zoom level and tile coordinates from Google Maps.
Compute a matrix of travel distances and durations between multiple origins and destinations using Google Maps Routes API.
Fetch a Street View map tile for a given panorama ID and XYZ tile coordinates.
Returns turn-by-turn directions between an origin and destination using Google Maps, supporting driving, walking, cycling, and transit modes.
Fetch the root tileset JSON for Google Maps 3D tiles to enable 3D map rendering in applications.
Estimate a device's geographic location using Wi-Fi, cell tower, and IP signals via the Google Maps Geolocation API.
Snaps a sequence of GPS coordinates to the most likely roads they were recorded on using the Google Maps Roads API.
Look up a multi-day weather forecast for a given location using Google Maps Platform's Weather API.
Fetch a static Street View image for any supported location using coordinates or a place name.
Search for places near a given location using Google Maps Places API, returning business listings and points of interest within a specified radius.
Retrieve solar potential data layers for a location, including roof segment analysis and irradiance data, via the Google Maps Solar API.
Returns a pollen forecast for a given location including type-level counts and risk index from Google Maps Platform.
Returns the time zone name, UTC offset, and DST offset for a given geographic coordinate and timestamp.
Returns an hourly weather forecast for a given location using Google Maps Platform's Weather API.
Look up current air quality conditions including pollutant levels and health recommendations for a given location.
Search for nearby places using the Google Maps Places API v1 by specifying a location and radius.
Look up current weather conditions for a given location using Google Maps Platform's Weather API. and 2 more.
Copy this prompt and paste it into your AI agent (like Claude, GPT-4, etc.) to enable automatic X-402 payment handling.
** Your task ** Call the API at: https://googlemaps.mpp.tempo.xyz Follow the steps below in order. ** Step 1 - Install FluxA Wallet CLI ** npm install -g @fluxa-pay/fluxa-wallet Or use without installing: npx fluxa-wallet <command> ** Step 2 - Register agent ** fluxa-wallet init --name "<YOUR_AGENT_NAME>" --client "<YOUR_CLIENT>" The response may include an authorization URL. Present the user with options: [Yes, open the link] [No, don't open]. If YES: run 'open "<URL>"' to open in their browser. Verify: fluxa-wallet status ** Step 3 - Discover endpoints ** curl https://googlemaps.mpp.tempo.xyz Returns JSON with: name, description, endpoints (paths, methods, descriptions, prices), paymentRequired, and networks. ** Step 4 - Choose payment method ** Ask the user: [On-chain USDC (Base)] or [FluxA Monetize Credits] If USDC: - --currency USDC - --amount in atomic units (6 decimals, e.g., 100000 = 0.10 USDC) If Credits (1 credit = 1 USDC): - --currency FLUXA_MONETIZE_CREDITS - --amount in 2-decimal units (e.g., 10 = 0.10 credits, 100 = 1.00 credits) ** Step 5 - Create an intent mandate ** x402 v3 uses intent mandates: the user pre-approves a spending plan (budget + time window), then the agent makes autonomous payments within those limits. fluxa-wallet mandate-create \ --desc "Spend up to <BUDGET> for <DESCRIPTION> valid for <DURATION>" \ --amount <BUDGET_IN_UNITS> \ --seconds <DURATION_IN_SECONDS> \ --currency <USDC or FLUXA_MONETIZE_CREDITS> Options: - --desc (required): Human-readable spending plan description - --amount (required): Budget in units for the chosen currency (see Step 4) - --seconds (optional, default 28800 = 8h): Duration in seconds - --currency (optional, default USDC): USDC or FLUXA_MONETIZE_CREDITS ** Step 6 - Get user to sign the mandate ** The response from Step 5 includes mandateId and authorizationUrl (TTL: 10 minutes). Present the user with options: [Yes, open the link] [No, don't open]. If YES: run 'open "<authorizationUrl>"' to open in their browser. ** Step 7 - Wait for mandate to be signed ** fluxa-wallet mandate-status --id <MANDATE_ID> Poll until mandate.status is "signed". The response also includes remainingAmount. Important: Use --id, not --mandate. ** Step 8 - Call the API ** curl https://googlemaps.mpp.tempo.xyz Optionally add the X-Agent-ID header for agent attribution (its value is the agent_id from 'fluxa-wallet status'): curl -H "X-Agent-ID: <YOUR_AGENT_ID>" https://googlemaps.mpp.tempo.xyz If it returns HTTP 402, continue to Step 9. ** Step 9 - Pay via x402 v3 ** Pass the complete HTTP 402 response body as --payload: fluxa-wallet x402-v3 \ --mandate <MANDATE_ID> \ --payload '$PAYLOAD_402' The payload must contain an accepts array. Do NOT extract individual fields - pass the entire 402 response JSON. The response includes xPaymentB64 (the payment token). ** Step 10 - Retry with payment token ** Retry the same request with the X-Payment header (optionally add X-Agent-ID for attribution): curl -H "X-Payment: <xPaymentB64>" <ORIGINAL_API_URL> Return the raw API response to the user without post-processing. ** Opening links for user ** Whenever you need to open a URL (authorization, approval, or any external link): 1. Present the user with a choice using your interactive options/menu capability (e.g., AskUserQuestion tool) 2. Options: [Yes, open the link] [No, don't open] 3. If YES: run 'open "<URL>"' to open in their default browser 4. If NO: ask how they would like to proceed ** Error handling ** - mandate_not_signed: User hasn't signed yet - ask them to open authorizationUrl - mandate_expired: Time window passed - create a new mandate - mandate_budget_exceeded: Budget too low - create a new mandate with a higher limit - agent_not_registered: No Agent ID - run 'fluxa-wallet init' first - Invalid payload: missing accepts array: Pass the full 402 response JSON
Want to combine multiple APIs into one skill? Browse All APIs →

