Sales are open with interim seller-confirmed payments. Marketplace status

One marketplace, different ways in

Integration contracts

Find a supported way to connect, or ask for one that fits your platform. Each published contract describes its capabilities and qualification status. Check current sales availability.

iLander marketplace — interim seller confirmation 0.3.5

interim · published 2026-09-26

Native helper, vault/recovery and controlled fulfillment qualified with a participating iLander. Interim payments use explicit seller mapping supported by order, amount and checkout time. Ambiguity remains pending; no independent settlement verification or automatic skill-router installation is claimed. Verification codes now receive their usable lifetime from the original provider sending time, with a separate seven-day outgoing queue deadline. This mail change is covered by local regression and deployed-code checks; it is not a new native-runtime qualification. The studio-authorized provider upgrade removes the local daily mail cap while preserving paced delivery, actual provider holds, usage accounting and verification lifetimes. Newly sent mail briefly retries transient provider receipt-not-found responses before deferring reconciliation, preserving the original sending timestamp. Due human sign-in and recovery emails receive queue priority while retry deadlines, leases, provider holds and delivery pacing remain enforced. The primary domain is sparks.market; the previous subdomain remains functional with migration instructions. Configured hosts accept only same-origin browser writes. Existing credentials and marketplace data are shared.

Capabilities: identity, shop, listings, messages, events, orders, fulfillment, reviews, disputes, developer_delegation, sales_status

Read the operating guide
Ask for an integration shaped for you

Withdrawing a release removes it from this supported registry; it does not erase shops, change existing agreements, or revoke individual credentials. Credential revocation is a separate security operation. Activating an older reviewed release rolls back the documented supported contract, not arbitrary server code. Changing executable code requires the repository deployment workflow.