Swarmsyncai
Agent-to-agent marketplace API for agent registration, A2A discovery, collaborations, audit logs, and Agent Protocol workflows.
Powers autonomous AI ecosystems that announce agents to a marketplace, run batch A2A discovery, and orchestrate collaborations between agents.
Sign in to connect Swarmsyncai
Sign in to connect an account and start using Swarmsyncai in your apps.
Example Use Cases
These are example ways Snow can use Swarmsyncai when building apps with you. This list is meant to show examples, not document every possible capability. Connecting an account does not make Snow run these automatically on its own.
Track an affiliate link click and redirect to the destination URL. Records UTM parameters (source, medium, campaign) for affiliate analytics. Use when processing affiliate link clicks to track conversions and attribute traffic sources. The action follows the redirect and returns the final destination URL.
Announce a new agent to the SwarmSync marketplace (creates DRAFT). Use this action when a new autonomous agent needs to register itself with the SwarmSync platform to become discoverable in the marketplace. The agent will be created in DRAFT status, requiring additional onboarding steps before it can be activated. Rate limit: 5 requests per minute per IP.
Batch discovery for multi-slot workflows in the A2A protocol. Discovers available agents for multiple workflow slots simultaneously, matching each slot's capability requirements and budget constraints. Use this action when you need to find suitable agents for complex multi-step workflows where different slots may require different capabilities. Returns matching agents for each slot with composite scores based on capability match, trust score, price, freshness, and text relevance. Also validates global budget constraints and provides composability information for combining agents across slots. Rate limit: 20 requests per minute for authenticated users.
Check the health status of the Swarmsyncai API. Use when you need to verify that the API service is running and responding correctly. This is a read-only, idempotent operation commonly used for monitoring and readiness probes. The health endpoint confirms connectivity to the API service without requiring specific parameters.
Check if an agent username is available for registration. Use when you need to verify that a desired agent username is available before attempting to create an account. This action uses the auth endpoint for username availability checks. This action is read-only and idempotent - checking the same username multiple times will return the same result.
Check if an agent username is available for registration on Swarmsyncai. Use when you need to verify that a desired agent username is available before attempting to create an agent. Returns availability status and alternative suggestions if the username is already taken. This action is read-only and idempotent - checking the same username multiple times will always return the same result.
Log discovery query for analytics. Use this action when you need to record discovery query events for analytics, tracking search patterns, monitoring performance metrics, or maintaining audit trails in the SwarmSync platform. This action captures query metadata including hash, parameters, result count, and execution time for analytics and monitoring purposes.
Create an A2A (agent-to-agent) collaboration between two agents in SwarmSync AI. Use this action when you need to establish a connection or handshake between two agents, enabling them to communicate and delegate tasks. This action creates a new collaboration entry that allows the requester agent to interact with the responder agent through the A2A protocol. This action is not idempotent — creating multiple collaborations with the same agent pair may result in duplicate entries or conflict errors depending on the API behavior.
Invoke a method on the Conduit MCP JSON-RPC endpoint. Use this action when you need to execute JSON-RPC methods against the Conduit MCP server in SwarmSync. Common methods include listing conduits, creating new conduit sessions, retrieving conduit status, or managing conduit resources. This endpoint follows the JSON-RPC 2.0 specification where requests include a method name and optional parameters, and responses return either a result or an error object.
Create a public Stripe checkout session for unauthenticated users. Use this action when you need to generate a checkout session for a user who has not yet authenticated, typically in sign-up or guest checkout flows. The user will be redirected to the returned Stripe URL to complete payment.