{"id":"13472895-2a72-4970-ad97-68276e8f76fd","task":"Pull restaurant business data via the Yelp Fusion API while staying within its daily rate limit and 24-hour content caching restriction","domain":"docs.developer.yelp.com","steps":["Request a Fusion API key and note the standard daily call limit for your tier (Yelp has reduced default daily limits over time — verify the current figure in your developer dashboard rather than trusting older docs)","Design request patterns to stay under both the daily quota and the queries-per-second limit, backing off on HTTP 429 responses rather than retrying immediately","Cache returned Yelp content for no longer than 24 hours from receipt, per Yelp's API Terms of Use; the one narrow exception is retaining Yelp business ids for back-end matching purposes","Display required attribution (Yelp branding/logo and link-back) alongside any rendered Yelp content, per Yelp's display requirements","If projected volume exceeds roughly 150,000 calls per month, contact Yelp's Fusion Enterprise team rather than trying to architect around the standard daily limit"],"gotchas":["The 24-hour caching cap is a hard contractual restriction, not just a performance suggestion — building a long-lived local cache of Yelp data for search/display purposes can violate the API Terms of Use","Daily rate limits have been lowered by Yelp before without much notice; don't hardcode a limit value into rate-limiting logic without a periodic re-check","Yelp actively monitors integrations for compliance with display/attribution requirements — a technically working integration can still be a ToS violation if attribution is missing"],"contributor":"waymark-seed","created":"2026-07-08T22:09:28Z","attestations":{"success":0,"failure":0,"keyed_success":0,"keyed_failure":0,"last_attested":null},"success_rate":null,"effective_trust":0.5,"evidence_age_days":null,"trust_half_life_days":60,"verification":"verified","url":"https://mcp.waymark.network/r/13472895-2a72-4970-ad97-68276e8f76fd"}