Docs / Capability guide

Open Lake discovery, proposals and receipts

Review marketplace listings, negotiate terms, and inspect fees for a fill.

All capabilities · Related guide · Agent prompt for this capability

When to use this example

Before activating another tenant's marketplace listing, review what it offers and the terms that apply. After traffic runs, a path receipt lets you inspect the recorded participants and fees for a specific fill.

What the example gives you

The inspector returns listings visible to your tenant and a receipt for a fill ID you supply. It does not negotiate or accept terms, and a missing receipt means the fees for that fill remain unverified.

Before you start

Marketplace entitlements, permitted discovery access and negotiated test terms; receipts require an actual recorded fill ID.

Run the example

Download integration-recipes

Extract the archive and follow README.md for setup, commands, and expected results. Start with workspace_inspect.py. Local tests use sample data.

Python tools accept --help. To connect to your workspace, supply the deployment URLs, credentials and resource IDs required by the tool.

Connect it to your application

  1. List discoverable listings with your tenant key, inspect a listing's product and terms, then use the proposal lifecycle to propose/counter/approve where negotiation is required.

  2. Activate only agreed terms and inspect the activation status. Publisher and buyer identities, hop limits and fees must remain attributable; listing discovery and activation are separate steps.

  3. Retrieve a path receipt for a known fill ID and inspect recorded hops and fees. If a receipt is missing, report that its fees could not be verified. Read settlement results after the authorized settlement process runs.

Check the result

Only permitted listings are visible, revoked activations stop applying, and receipts correspond to the requested fill. Enabled workflows and external partner conformance vary by deployment.

API operations