# Synapse Lounge x402 Service Manifest

> Synapse Lounge x402 Service Manifest is a paid API for AI agents from synapse-lounge.synapse-lounge.workers.dev, paid per call via x402, $0.01/call, status unknown (last checked 2026-10-10).

Returns the service manifest and x402 access metadata for the Synapse Lounge API, describing available endpoints and service status

## Facts

- Endpoint: GET https://synapse-lounge.synapse-lounge.workers.dev/api/x402?utm_source=zero.xyz
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-10
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/synapse-lounge-x402-service-manifest-1c696305
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_ABkGFqfELQtW58SsjuS3s

Status and success rate cover calls made through Zero and Zero's own probes. Third-party monitors may report differently.

## How to call it through Zero

Zero handles the 402 payment challenge and records the run. With the Zero CLI installed (`npm i -g @zeroxyz/cli`):

```sh
zero fetch --capability synapse-lounge-x402-service-manifest-1c696305
```

Example prompt: Pull up the Synapse Lounge service manifest so I can see what's available and check whether the MCP endpoint is active.

## When to prefer this

Use this endpoint when an agent needs to discover or verify the Synapse Lounge service configuration, MCP endpoint URL, or operational status before making downstream calls. It is the canonical entry point for x402 manifest inspection on this platform.

## Known failure modes

- Service unavailable on Cloudflare Workers edge — returns 5xx
- Payment not processed — returns 402 Payment Required if x402 protocol handshake fails
- Invalid HTTP method — only GET, HEAD, DELETE are accepted; POST or PUT returns 405
- No matching query parameters accepted — additionalProperties is false so unexpected params are rejected

## How this service works

Synapse Lounge x402 access and service manifest

## Output

Returns a JSON object containing the service name, current status string, and MCP endpoint URL, along with any additional metadata fields describing the Synapse Lounge x402 service configuration.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "$schema": "https://json-schema.org/draft/2020-12/schema",
 "required": [
  "input"
 ],
 "properties": {
  "input": {
   "type": "object",
   "required": [
    "type",
    "method"
   ],
   "properties": {
    "type": {
     "type": "string",
     "const": "http"
    },
    "method": {
     "enum": [
      "GET",
      "HEAD",
      "DELETE"
     ],
     "type": "string"
    },
    "queryParams": {
     "type": "object",
     "properties": {},
     "additionalProperties": false
    }
   },
   "additionalProperties": false
  },
  "output": {
   "type": "object",
   "required": [
    "type"
   ],
   "properties": {
    "type": {
     "type": "string"
    },
    "example": {
     "type": "object",
     "required": [
      "service",
      "status",
      "mcp"
     ],
     "properties": {
      "mcp": {
       "type": "string"
      },
      "status": {
       "type": "string"
      },
      "service": {
       "type": "string"
      }
     },
     "additionalProperties": true
    }
   }
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/synapse-lounge-x402-service-manifest-1c696305/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from synapse-lounge.synapse-lounge.workers.dev](https://www.zero.xyz/host/synapse-lounge.synapse-lounge.workers.dev/llms.txt)