landfeedAPI · MCP · 2.0.0PolskiAgent Markdown

Rate and size limits

HTTP 429 refuses admission because of request rate, concurrency or credits. Inspect the body, account balance and Retry-After when present. Back off with jitter and reduce concurrent reads. Never automatically replay payments, confirmed ask actions or webhook registration.

InterfaceLimit
ask6/min/account; 2 concurrent/process
MCP600/min/account/process; 30/min anonymous/process
watch30/min/account; includes invalid requests
watch body256 KiB; 100 items; 1024 vertices total
ask bodyask-v1: 16 KiB; ask-v2: 1 MiB
ask results40; 512 000 bytes
ask artifact192 000 bytes/artifact; 480 000 bytes/turn
ask messages64 000 bytes; last 20 in planner
ask continuation3600 s
Ask request budget120 s; LANDFEED_ASK_REQUEST_SECONDS
SSE keepalive10 s; : keepalive
SSE backpressure5 s
MCP body64 KiB
billing body64 KiB
/.well-known/oauth-authorization-server600/min/process; 16 KiB
/register30/min/process; 16 KiB
/authorize120/min/process; 16 KiB
/oauth/consent120/min/process; 16 KiB
/token300/min/process; 16 KiB
/revoke300/min/process; 16 KiB
Stripe webhook600/min/process; 64 KiB
checkout / checkout_reconcile / team_invite10/min/pool/operation

Process-local limits are not global throughput guarantees. Shared credit balances and watch-item entitlements can refuse work earlier. There is no single declared requests-per-second promise for all REST reads. The local stdio MCP bridge caps decoded bodies at 16 MiB and total HTTP time at 30 seconds; timeout leaves billing unknown.

Search has its own area/cursor/filter bounds. Read the operation schema rather than treating the batch limit as a search limit. The schema reference and operation availability distinguish definitions from executable runtime features. Operations marked x-runtime-supported: false remain unavailable even though their schemas exist.

After an interrupted response, retain the request id and reconcile billing before replay. The errors catalogue gives code-specific recovery actions.