Good Earth

Generate a patron's account statement at this operator. Returns the patron's purchase history, active credit tranches, per-tool usage breakdown, and recent daily usage logs. This is the patron's spending account — not the operator's Authority tax balance. Free — no credits consumed. Proof of npub ownership is required to prevent statement-scraping of arbitrary patrons.

Generate a visual SVG infographic of your account statement. Returns the same data as account_statement, rendered as a dark-themed SVG graphic with balance hero, metrics cards, health gauge, tranche table, and tool usage breakdown. Costs 1 api_sat per call. Proof is verified by ``debit_or_deny`` before any cost is incurred.

Check this operator's adoption-request status at a chosen Authority. Free. Polls the Authority MCP-to-MCP for the status of this operator's request (pending / approved / rejected / provisioned).

The sky's own record for this ground — normal, actual, and what is coming. Degree days say what the season is doing to the plants. This says what the season is doing: temperature, dew point, rain, wind, sunshine and day length, each against what is normal here, what has actually happened, and the fortnight ahead. Plus the sun and moon, which are astronomy and so are computed exactly rather than forecast. Growers read these together with the heat. A week of high dew points is disease weather whatever the degree-day total says, and a dry August is an irrigation decision that heat accumulation cannot make for you. One call covers every measure — three upstream requests regardless.

What you grow, watch for, or saw on a plot — a page at a time. `as_of` is how a past season answers: the record as it stood that day, rather than as it stands now. Sorting and searching happen in the database, over as many rows as the block holds rather than the page you are looking at.

Record what you grow, watch for, saw, or hold seed for on a plot. A whole batch in one call, because an afternoon in the field produces several notes at once and each one should not be its own fare.

The ground you have saved, with its bounds. The blocks themselves and nothing else — what grows on them, what you watch for, and what you have seen are their own listing, so this answer stays the same size whether you farm one plot or forty. A grower who has saved nothing gets the worked example, marked as such, so there is always somewhere to stand. Blocks can overlap — a meadow drawn inside the farm that contains it is two blocks, each answered for its own ground. Read an overlap as intent, not as one outline being wrong. Each block names its `groups`. A group path like 'North Farm / Orchard' sits inside 'North Farm'; `group` lists one group with everything inside it.

Save a plot of land, so every other tool can work it by name. Several at once go in `blocks`: a whole layout in one call, because a garden subdivided into beds produces many blocks at once and each one should not be its own fare. Its area and sample count are measured here from the bounds you give, and returned — they are facts about the geometry, so there is nothing for you to keep in step. Blocks may overlap or nest. A grower who saves the whole farm and then the meadow inside it has asked two questions about two pieces of ground, and both are right; the overlap is not a drawing error to correct.

Propose bed layouts inside a plot. Writes nothing. Reads the plot's outline and returns `variants` layouts, each with its metrics (beds, path share, worst and median compactness, narrowest path, and for rows the row-metres, turns and headland share), warnings, a small SVG preview, and `accept.blocks`: the exact list to pass to goodearth_block_save(blocks=…) to keep it. Blocks already inside the plot are retired under a `v1 ` name in that same list, so the old layout stays readable and its names are free. The new beds are saved in a group named for the plot, inside each group the plot is in. A layout over 100 blocks comes as `accept.batches`, saved in order. Paths are the space between beds, kept at the width asked for after the edges are softened. Below one terrain cell (about 90 m) neighbouring beds share a climate sample; the warning says so, because the beds are then bookkeeping and the climate answers stay at the plot's scale.

Compute this block's dated season as a dataset, and store it for publishing. Every dated thing this block knows about: crop targets, pest stages, wildlife and husbandry dates, the frost record, and your tasks. Returned as structured rows — a calendar is one rendering of them, and a caller wanting a table or a notification wants the same data. An iCalendar rendering is stored alongside under a feed token, which the Good Earth site serves at a subscribable URL. Point any iCal or Google Calendar client at it and the season appears next to the school run and the market stall, which is where a grower will actually see it. This is the computed act: it reads the weather feeds and rebuilds everything. Pass the same token again to recompute in place — subscribers keep their subscription and the events update rather than duplicating. Nothing is passed in but the block: what it grows, what it watches for and what is due are read from the record. That is what makes a refresh safe — while those collections travelled as arguments, nobody could recompute an existing feed without knowing what had been handed to it the first time, so a refresh silently published a smaller season than the one it replaced.

Read a stored calendar dataset by its feed token. This exists for the Good Earth site, which serves the subscribable URL: a calendar client speaks HTTP and knows nothing about MCP, JSON-RPC or npub proofs, so the site fetches through here and renders the response as text/calendar. The unguessable token is the credential — there is nowhere in an iCalendar subscription to put a proof. Serving is a separate act from computing, and every read is counted so the operator can see how hard a feed is worked.

The calendar feeds you have published, and how often each is polled.

Stop publishing a feed. Subscribers stop receiving updates. Free.

Turn a block's own field reports into a correction on the model. Every other tool here answers from a 9 km grid refined by a physical terrain model. What that cannot know is the part that makes a farm particular — the hedgerow, the pond, the outlet the cold air drains through. Your observations measure exactly that gap. Returns two corrections, kept separate because they fix different things: a bias in *heat* from crop stages (this ground accumulates more or less than the grid credits) and a bias in *days* from observed frost (this ground frosts earlier or later than the region). The block's sunlight reports are counted and pointed at goodearth_sunlight, which reads them. Nothing is applied silently. A correction appears only once several observations agree, implausible values are set aside rather than averaged in, and the reports behind every figure come back with it.

Check this operator's tax balance at the Authority. Returns the sats available for certifying patron credit purchases. When this balance reaches zero, patron top-ups cannot be certified and the operator must call purchase_credits on the Authority. This is the operator's own funding — not a patron balance. Free.

Check a patron's credit balance at this operator. This is the patron's spending balance — credits purchased via Lightning for tool calls at this operator. For the operator's own balance at the Authority (needed to certify patron purchases), use authority_check_balance instead. Free — no credits required. Proof of npub ownership is required to prevent anyone-with-the-registry from enumerating balances.

Check the payment status of a Lightning invoice. Call after paying the invoice from purchase_credits. Free — no credits required. Proof of npub ownership is required to prevent credit-grant front-running by an observer of the invoice ID.

Preview the effective cost of a tool call. Shows the base cost and any constraint effects (discounts, free trials, surge pricing). Free — no credits required.

Check whether a proof grant is still valid. Mirrors ``check_oauth_status`` for the npub-proof flow: a calling agent can ask "will my next paid call accept this dpop_token?" before burning credits on a guaranteed failure. Expiry is read from the grant itself; the only store consulted is the patron's revocation watermark. Free, no side effects — touches no relay.

Companions for one planting on this block, of one of two kinds. **Synergy** reads the planting's family and genus from iNaturalist and applies published companion-planting rules — nitrogen fixers beside heavy feeders, open flowers that feed the wasps that take aphids, alliums that mask a carrot from its fly, walnut and fennel that poison the ground beside them, the same family sharing its pests. Every row names its mechanism or its tradition and a citation. These rules Good Earth publishes rather than computes; it says so in the note. **Design** is arithmetic over what you wrote down: a colour opposite on the wheel is complementary, beside it analogous, white a foil; a plant in a different height band layers; two that bloom in the same months are seen together. A planting with no `flower_color` gets the field named rather than a guess. Candidates are the plantings on this plot, then everything you have grown on your other blocks or retired, then a few classic garden examples — each row says which. Plantings with no species chosen are listed as `unplaced`; a typed name is never guessed into a family.

Where every planting on a block stands, and whether it finishes before frost. Returns, per planting: heat accumulated since set-out against its target, the projected date it reaches that target at the season's recent rate, and a verdict on whether that lands before the median first frost. One call answers the whole block. The season curve and the frost record are shared across plantings, so asking about eight beds costs one round trip rather than eight.

Which crops finish on this ground, and with how much room to spare. "What can I grow?" is not a lookup. Two farms in the same county, one on a bench and one in a hollow, have different answers — so this measures the block's own frost-free window and the heat it accumulates inside it, then judges each crop's requirement against that. The answer that matters is not yes or no but MARGIN: how much season is left after the crop is done, in the days a grower plans in. A crop that finishes on the last warm day of an average year fails in half of them. Requirements are yours. Published degree-day figures vary by cultivar and maturity group; Good Earth computes against your ground rather than publishing agronomy.

Delete a coupon. Cascades to all patron redemptions. Any chain step referencing the deleted coupon_id becomes a no-op (the constraint returns neutral on unknown ids) — the Studio surfaces orphan references as warnings. RESTRICTED to operator — requires proof.

Remove a single operator secret field. Deletes one key from the operator's encrypted credential blob without touching the others — the field-level counterpart to ``forget_credentials``, which wipes the whole row. Use it to retire a leftover after an SDK cutover (a Prefect key after Modal, or a stored but untemplated orphan like ``anthropic_api_key``) without taking the operator down for a full re-delivery. Stored-but-untemplated fields are first-class: the delete is keyed on what is vaulted, not on what the current template declares. Idempotent — already-absent fields report ``removed: false`` without rewriting the vault. RESTRICTED to the operator — requires the operator's proof (a kind-27235 event or a proof grant); patron proofs are rejected. A deletion is as destructive as a write.

Remove a single patron credential field. Deletes one field from stored credentials without affecting other fields. Free. Proof of npub ownership is required — this is a write to the patron's sensitive credential vault.

Hours of leaf wetness on this ground, and what the disease models make of them. Returns the estimated wet hours since the season began, every qualifying infection period each model found, which of its criteria were met and which were not, and the wet stretch the forecast implies next. Degree days are the wrong clock for a fungus. What decides an infection is how long the leaf stayed wet and how warm it was while it did, which is why a dry August that accumulated heat all month grows no botrytis. A season with nothing qualifying is reported as exactly that — risk that is absent is as useful to a grower as risk that is present. WETNESS IS ESTIMATED, NEVER MEASURED. No feed publishes a leaf wetness sensor for arbitrary ground, so it is inferred from modelled humidity and rain, and every answer names the estimator and the feed that fed it. That matters more here than elsewhere: humidity crosses the 90% line in a step, and two feeds a couple of degrees apart on dew point can differ threefold on the hours they count. Good Earth runs published models against your ground. It does not publish plant pathology and it never recommends a treatment — registration is jurisdiction-specific and a label rate is law. Take the decision to your extension service, whose word counts where this service's does not.

When the dew burns off this ground, the dry days ahead, and the next rain. Answers "is it dry enough yet?" for a grower planning to cut flowers, pick, mow or make hay. Returns this morning's and tomorrow morning's dew-off hour (the first hour the leaves are estimated to stay dry for two hours running), the first run of forecast days with no rain, the next hour of rain, and per day the rain, wet hours, reference evapotranspiration (FAO-56 ET0) and peak vapour-pressure deficit — how hard the air is pulling water out of anything wet. Ten days ahead, from one forecast call. Not wet is not drying: a still, overcast, humid day wets nothing and dries little, which is why ET0 travels with every day. Wetness is ESTIMATED from modelled humidity and rain, never measured, as in `disease_risk`. Conditions only. Good Earth never says a crop is ready to cut or that hay will cure — that depends on the crop, the swath and the field — and it publishes no agronomy.

Remove a coupon from this patron's redemption list. Cosmetic only — the coupon itself still exists at the operator, and the patron can re-redeem the same code later while the window allows. Free — requires proof of ``npub``.

Delete vaulted credentials for a specific service and npub. For operator credentials, pass the operator's own npub. For patron credentials, pass the patron's npub. Always requires proof of npub ownership — a deletion is as destructive as a write.

Delete every block you have here, and everything recorded on them. Blocks, crops, plantings, pest models, wildlife watches, field reports, tasks, published calendar feeds and the cached weather read for your ground. A real delete, not a retirement: every other removal in this service keeps the row as history, and this one does not, because a grower who asks to be forgotten and is quietly kept has been told something untrue. Any calendar feed you published stops resolving at once. **You remain a patron.** Your balance and your purchase history are not touched — those are the network's ledger rather than this operator's record of your farm, and there is no name, email or KYC in this system to forget. Sign in again with the same npub and you can start over on new ground. Requires proof of the npub, like any call that reads your record. Free: charging someone to leave is a toll on the door out.

When frost normally arrives on this ground, and whether it is coming this week. Returns first-frost dates from the last ten seasons, how far the region's own terrain spreads that, and a night-by-night assessment of the coming forecast for the *coldest* ground rather than the average. A season begins where this ground's own record never frosts — mid-July in Vermont, mid-January south of the equator — given as ``first_frost.season_starts``. ``this_season`` is the season so far, up to yesterday: its first frost, or with none yet, ``given_none_yet`` — when the seasons still frost-free by now went on to frost, which is the answer once the median has passed. The spread is the answer's point. Frost forms on still, clear nights when cold air drains off high ground and pools in low, so a single forecast low is optimistic for a hollow and pessimistic for a bench on the same block.

Growing degree day accumulation across a region, season to date. Returns accumulation with its spread across your ground, the band of the last ten seasons to read it against, a 7-day forecast extension, and a projection at the recent rate. The spread is the answer's point: it says how much the same field varies from bench to hollow, which is what decides whether one planting date serves the whole block.

Read an npub's public Nostr profile (NIP-01 kind-0 metadata). Free, no proof — the data is already public on relays. Returns the latest metadata fields (name, display_name, about, picture, banner, nip05, website, lud16) or an empty profile if none is published.

Generate a Merkle inclusion proof that a patron's balance was included in a Bitcoin-notarized snapshot.

Report this operator's configuration readiness. Shows which operator settings are configured, which are missing, and how to deliver each missing value. For patron-level credential status, use get_patron_onboarding_status instead. Free.

List stored patron credential field names (not values). Returns the names of fields stored for a patron, plus each field's ``delivered_at`` ISO-8601 timestamp when known (null for secrets vaulted before timestamps were recorded). Values are never exposed — use this to verify which fields are configured and how old each one is. Free. Proof of npub ownership is required: the list of configured fields is itself sensitive (reveals which integrations a patron has set up).

Report a patron's credential readiness for this operator. For set-once services (eXcalibur, TheBrain), shows which patron secrets are configured and which are missing. For dynamic/OAuth2 services (Schwab), reports that no patron credentials are needed. Free. Proof of npub ownership is required because credential presence is sensitive information about the patron's setup.

Get the active pricing model for this operator. Free. If no model exists, self-initializes a scaffold with all registered tools at 0 sats. No economic data from code.

Return canonical (tool_id, mcp_name, …) for every tool the wheel exposes. The authoritative source for any client (Studio, agents, FE) that needs to know how this MCP identifies its tools. Reconcile uses this output to UUID-join against the stored pricing model — no name-based UUID derivation, no guessing. Includes both ToolIdentity-seeded tools and any UUID recorded by ``@paid_tool`` that is missing from the registry. The latter appear with ``registered: false`` (and in the top-level ``unregistered`` array) so Reconcile can flag deploy drift instead of silently reporting clean when a live tool was never seeded (#174). If the operator renames a function or rebrands a slug, the mcp_name in this output changes but tool_id stays. That's the whole point of the canonical-UUID design. Also diffs the live FastMCP wire surface against the registry. Tools exposed on the wire but absent from the registry appear in ``unregistered`` so Reconcile can flag deploy drift instead of silently under-reporting (issue #175). Free, no side effects.

List all available constraint types and their parameter schemas. Returns the type, category, description, and parameter specs for every constraint that can be used in a pricing pipeline. Free — no credits required.

List every coupon this operator has minted (newest first). Each row carries the current ``times_redeemed`` counter — the Studio renders a progress bar from this against ``total_uses``. RESTRICTED to operator — requires proof.

List the coupons this patron has redeemed on this operator. Returns both active and exhausted redemptions with a per-row ``status`` (``active`` / ``window_closed`` / ``patron_limit`` / ``total_limit``). Free — requires proof of ``npub``.

List recent Bitcoin notarization records.

Create a new operator-owned discount coupon. The coupon owns its binding: ``tool_ids`` names the tools it discounts, and re-pricing a tool never touches it. A coupon bound to no tool discounts nothing, however many patrons redeem it.

Search what is actually recorded near this ground, a page at a time. This replaces asking for a whole catalogue. There are more than three thousand insect and spider species recorded around one Vermont block; the old answer showed forty of them and said nothing about the rest, and fetching all of them costs eleven round trips to build a list nobody reads. So: search, twenty to a page, and the true total on every page. **Species are a landscape fact, not a field one.** A nine-hectare hayfield contains almost no observations, so the search widens to the surrounding country and the answer says how wide it looked. Every other tool here answers about the drawn ground and nothing outside it; this one cannot. **The count measures observers as much as organisms.** A roadside is better recorded than a back hayfield, so a high count is evidence somebody was standing there — not that a thing is common on your ground. No judgement of any kind. iNaturalist does not say which of these is a pest, a weed, or worth planting, and sorting them into those would be adding a claim the feed never made.

Build a Merkle tree of all patron balances and submit the root to Bitcoin via OpenTimestamps. Operator-only background task. Bitcoin confirmation takes 1-6 hours. Free — no credits required.

Describe the DPYC ecosystem via the Oracle. Free.

Get the current DPYC certification tax rate. Free.

Get DPYC onboarding instructions from the Oracle. Free.

Look up a DPYC community member by npub. Free.