GoodAPI: Plant Trees

@GoodAPI: Plant Trees show me all tree plantings from the last 30 days with metadata tag 'customer-offset'

Found 47 tree-planting registrations tagged 'customer-offset' from the past 30 days. Total trees: 1,203. Breakdown: 28 registrations (840 trees) in Kenya, 12 registrations (240 trees) in Madagascar, 7 registrations (123 trees) in Haiti. Most recent planting: 50 trees registered 2 days ago with attribution ID 'order-8472'. All registrations show 'active' status. Note: This list reflects registrations created in your account; field planting typically occurs 2-4 weeks after registration.

This example demonstrates filtered retrieval across your organization's planting history. The MCP returns all matching records without pagination, so narrow your date range or metadata filters when querying accounts with thousands of plantings. Requires read scope on your GoodAPI key.

@GoodAPI: Plant Trees create a planting for 25 trees with idempotency key 'user-signup-xyz-001' and metadata customer_id='xyz'

Tree planting created successfully. Registration ID: plt_9k3mF2aB7. 25 trees registered for planting in Kenya (estimated field planting: 14-21 days). Idempotency key 'user-signup-xyz-001' recorded — reuse this exact key only if retrying this identical request. Metadata attached: customer_id='xyz'. Note: Live API keys incur charges immediately upon registration. Current account balance will reflect this planting within 60 seconds.

This example shows the core write operation that registers trees and triggers billing. Always use a unique idempotency key per distinct planting to prevent accidental duplicates. The MCP does not validate whether your key has funds before creating the registration — check your GoodAPI dashboard for billing alerts if operating near account limits.

@GoodAPI: Plant Trees pull aggregate evidence data and summarize which regions have the most verified field photos this quarter

Aggregate evidence retrieved (data cached for 30 days, last updated 6 days ago). This quarter's verified field evidence: Kenya leads with 1,847 field photos across 412 planting sites, followed by Madagascar (1,203 photos, 287 sites) and Haiti (634 photos, 156 sites). Kenya's evidence includes GPS-tagged seedling photos, survival checks at 30/60/90 days, and community partner attestations. Note: This global dataset spans all GoodAPI customers, not just your organization's plantings. Use the registration-specific evidence endpoint to verify your own trees.

This synthesis example pairs the MCP's aggregate evidence tool with AI reasoning to surface regional trends. The returned data is global and cached for 30 days, so it's useful for general transparency reporting but not real-time verification of your specific plantings. Media lists can be large (hundreds of URLs); the AI summarizes rather than returning raw links.

When to automate tree planting for customer purchases

A 6-person DTC brand wants to plant a tree for every order over $50. The Create Tree Planting tool handles this if you can pass order metadata as the idempotency key and track attribution in your checkout flow. The MCP works when your order volume stays under 500 transactions per day—above that, the lack of pagination in List Tree Plantings becomes a bottleneck for reconciliation. Refund Tree Planting covers returns, but only within the current billing cycle, so you'll need a manual process for late returns. If your brand ships 10-30 orders daily and wants a public impact dashboard without building custom tracking, this MCP closes the loop in under an hour of setup.

Linking subscription tiers to verified tree planting

A 12-person B2B SaaS team offers a 'green tier' that plants 10 trees per user per month. The Get Impact Dashboard URL tool gives you a shareable proof page for marketing, and the List Tree Plantings API lets you filter by customer metadata for account-level reporting. This scenario wins if your pricing model already segments by user count and you can stomach the 30-day evidence cache—real-time verification isn't available. The idempotency key requirement means you need stable subscription IDs; if your billing system generates new transaction IDs on renewal, you'll double-count plantings. For SaaS teams with predictable user counts and a marketing need for third-party impact validation, this MCP delivers the dashboard in one integration sprint.

When aggregate evidence supports one-time campaigns

A 3-person nonprofit runs an annual fundraiser and wants to show donors the global planting impact their contributions funded. The Get Aggregate Planting Evidence tool returns region-grouped totals and field photos, but the 30-day cache means you can't pull fresh data for a live event dashboard. This MCP fits if your campaign wraps in a single month and you're comfortable with a static evidence snapshot for post-event reporting. The large media list can bloat responses, so budget extra time if you're rendering photos in a donor portal. If your event happens once a year and you need verified planting proof without building a custom integration with a tree-planting vendor, this MCP gets you public-facing evidence in under two weeks of dev work.