Add Macro Pulse (finance) provider

[benji7891]

Adds Macro Pulse — a pay-per-call macroeconomic indicator API for AI agents, sourced from World Bank Open Data (GDP growth, inflation, unemployment trend), synthesized into a single momentum score per country. Single-country lookups at $0.02, 8-country batch endpoint at $0.05. Settled in USDC on Base via x402.

• providers/macro-pulse/macro-pulse/PAY.md added following the format in providers/exa/search/PAY.md
• Live service: https://macro-pulse-x402.onrender.com
• OpenAPI: https://macro-pulse-x402.onrender.com/openapi.json

[greptile-apps]

Greptile Summary

Adds the Macro Pulse provider definition.

• Registers single-country and eight-country batch macroeconomic momentum endpoints.
• Declares per-request pricing and documents country-code inputs, caching, and x402 settlement.

Confidence Score: 3/5

The PR should not merge until the provider is verified to accept Solana-mainnet USDC or USDT and the payment instructions are corrected accordingly.

Both newly registered endpoints are paid, but the provider describes only Base settlement despite the registry requiring Solana-compatible payment for every paid endpoint.

providers/macro-pulse/macro-pulse/PAY.md

Important Files Changed

Filename	Overview
providers/macro-pulse/macro-pulse/PAY.md	Adds a structurally valid inline provider definition, but its documented Base-only payment rail conflicts with the registry’s Solana payment requirement.

_{Reviews (1): Last reviewed commit: "Add Macro Pulse (finance) provider" | Re-trigger Greptile}

[greptile-apps]

Payment rail violates registry contract

When either priced endpoint enters catalog validation, the provider documents only USDC on Base instead of the required Solana-mainnet USDC or USDT rail, causing a Base-only service to fail the compatibility gate and preventing publication; document Solana support accurately when the service provides it.

Knowledge Base Used: Provider registry (providers/)