landfeedPricing
Pricing is
not decided.
The plan prices requests, not tokens, with hard caps and no overage. The shape on this page is planned and subject to change. Billing and refund rules are already part of every response.
Already in the contract
What a request is.
One request, one answer
check, parcel, layer, resolve, search and events cost 1 request each. Batch costs 1 per item. /v1/sources and the OpenAPI cost 0.
You pay for answers
Charged: answers, informative negatives and candidate lists. Free: invalid input, a wrong key, a 304. Refunded: not found, other client errors, server errors, and anything not_covered.
Visible in every response
billing {cost, charged, refunded, rule} in the body, and X-Request-Cost, X-Credits-Charged, X-Credits-Refunded in the headers, so an agent can plan its spend.
Planned at release
Flat plans with hard caps and invoices with VAT. Metered overage is not in v1. Until release there are no keys for sale and no charges.
Waitlist
Hear when the hosted MCP opens.
Leave an e-mail address and we will write once, when https://mcp.landfeed.pl/mcp goes live.
Not connected yet: this form sends nothing until the waitlist service is set up.
Common questions.
Why requests and not tokens?
A request is something a vendor or a bank can budget. One request is one answer, whatever the size of the record behind it.
Will there be a free tier?
The plan includes one: 300 requests a month. Like every number on this page it is planned and may change before release.
How is monitoring priced?
Planned per parcel per month, quoted for each portfolio. Change history starts with the first precompute run in October 2026.
Do refunds need a ticket?
No. Refunds are applied in the response itself and shown in billing.refunded with the rule that decided them.