Skyfirev1.0.3

A marketplace seller agent needs to verify that all of its approved services are discoverable and correctly listed in Skyfire's directory. The agent calls get_services_by_agent to pull every active listing, then cross-checks against internal catalog data to spot missing or stale entries.

A buyer-side AI agent browses the Skyfire marketplace to find approved services that match a procurement request. It uses get_all_services to enumerate options and get_service to inspect specific candidates before shortlisting.

A team onboards a new autonomous buyer agent by creating a funded pay token scoped to one seller service or seller domain. The agent uses create_token to generate the pay and identity-carrying KYA variants so the buyer can transact within its allowed spend envelope.

An organization needs to give an agent a verifiable identity token that sellers can trust during transactions. It calls create_token to mint a KYA variant for a specific seller domain, then distributes it to the agent's runtime.

A seller operations team programmatically monitors which of its marketplace services remain approved and active. A scheduled agent runs get_services_by_agent on a recurring basis and alerts the team if listings drop out of the directory.

OOMOL charges the end user per Skyfire connector execution through its credit system, with billing enforced via the OOMOL_INSUFFICIENT_CREDIT stop. Users prepay credits and each oo connector run consumes from that balance.

OOMOL handles Skyfire API key storage and server-side credential injection, so teams never touch raw tokens. The connector layer is sold as a secure, managed integration for agents that need to transact or query the Skyfire marketplace.

By wrapping token creation and marketplace discovery behind a simple CLI, the skill lowers the barrier for developers and agent builders to participate in Skyfire's buyer/seller economy. Growth in agent-initiated transactions drives repeated connector usage.