Guide: Manage existing endpoints

Edit, pause/resume, and delete — available as MCP tools and REST. All are owner-scoped (you can only touch your own endpoints).

Edit

MCP tool update_endpoint, or PATCH /dashboard/endpoints/{endpoint_id}. Send only the fields you want to change:

{
  "endpoint_id": "…",            // MCP only; REST puts it in the path
  "name": "Weather Pro",
  "description": "Now with hourly data",
  "origin_url": "https://api.example.com/v2/weather",
  "method": "POST",
  "price_usd": "0.03",
  "networks": ["eip155:8453"],
  "auth_type": "bearer",
  "auth_value": "sk_live_new_key"
}

• price_usd / networks apply to API relays. Networks are reconciled to the set you send (removed networks are deactivated, added ones created); they must match the endpoint’s environment. (MCP-wrapper pricing is per-tool and edited separately — endpoint-level fields above still work for MCP wrappers.)
• Origin auth: set or rotate by sending auth_type (bearer | api_key | basic | custom) + auth_value (+ auth_header_name for api_key/custom); clear it with auth_type: "none". Omit these to leave the credential unchanged. This is how you rotate a leaked upstream key.
• Free ⇄ paid: send free: true to make an API relay free (clears its pricing — buyers then call it with no payment). Send free: false together with price_usd, networks, and pay_to to put a free endpoint back behind payment. In the dashboard this is the “Make this free” tickbox.

Your public profile

Your profile page lives at /u/<your-handle> — name, avatar, bio, type (individual / team / company), website, and social links. A complete profile builds buyer trust and is the page you share to show off your data.

Edit it three ways (same result): the MCP tool update_profile, PATCH /dashboard/profile, or the Public profile section of the dashboard. Read it back with get_profile (or GET /dashboard/profile). Only provided fields change; send an empty string to clear a text/URL field, and social_links (when given) replaces the whole map:

{
  "name": "Acme Data",
  "profile_type": "company",
  "bio": "Clean, fresh weather + market data for agents.",
  "avatar_url": "https://cdn.acme.io/logo.png",
  "website_url": "https://acme.io",
  "social_links": { "x": "https://x.com/acme", "github": "https://github.com/acme" }
}

Your handle (slug)

Your handle is the @you in /u/<you> and in your call URLs /r/<you>/<endpoint>. New accounts get an auto-generated one (your email prefix, or agent-xxxx for wallet sign-ups). Claim a real one by sending slug to update_profile / PATCH /dashboard/profile (lowercase [a-z0-9-], 2–39 chars, unique, not a reserved word). Check availability first with GET /dashboard/handle/check?slug=….

⚠️ Changing your handle changes your call URLs, so any URL a buyer already saved stops working. Claim a good handle early, before you have buyers.

The Verified badge is not self-serve — it’s granted by the team after a manual trust review.

Pause / Resume

• Pause: MCP pause_endpoint, or POST /dashboard/endpoints/{id}/pause → status becomes disabled. The endpoint stops serving (relay returns 404) and drops off the marketplace. In-flight is unaffected; new calls are refused.
• Resume: MCP resume_endpoint, or POST /dashboard/endpoints/{id}/resume → status back to active.

Delete

MCP delete_endpoint, or DELETE /dashboard/endpoints/{id}.

This is a soft delete: the endpoint is hidden from your list, taken offline, and its slug is freed so you can reuse the name. Payment history (PaymentAttempt — your revenue/audit records) is preserved. A deleted endpoint can’t be edited or resumed; recreate if you need it back.

Quick reference

Pricing changes take effect immediately on the next 402. A buyer mid-flight with an old quote simply gets a fresh 402 on retry.