gate402 merchant checkout

com.ogenalabsPublished by ogenalabs.comOfficial publisherv0.1.0Updated Oct 24, 2026

Drop-in x402 checkout for merchants: issue terms, verify payment. $0.01 each.

VerifiedStreamable HTTPWeb executableFinanceBusiness & Commerce

Overview

AI-generated overview

Remote x402 checkout adapter for merchants: an assistant can issue payment terms and verify payments through the hosted Ogena gate402 API.

What you can do
  • Issue checkout terms for a merchant payment
  • Verify an x402 payment against those terms
  • Call a hosted endpoint that performs the actual checkout logic
  • Use a demo storefront and agent skill docs as reference examples
When to use it
Relevant for merchants or agent builders who need an assistant to create x402 payment terms and confirm payment on the Ogena gate402 service, rather than for general payment processing.
Requirements
A remote streamable HTTP endpoint at api.ogenalabs.com; no local package, environment variables or headers are declared. Network access to the hosted API is required.
Before you install
Each checkout costs $0.01, so assistant calls can spend money; verification is described as free. The public repository holds only tool schemas and docs, while product logic runs on the hosted endpoint and its source stays private, so behavior cannot be inspected locally.

Installation

In SourceWeft

  1. Open gate402 merchant checkout in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/com.ogenalabs%2Fgate402-x402/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "gate402-merchant-checkout": {
      "type": "http",
      "url": "https://api.ogenalabs.com/api/gate402/mcp"
    }
  }
}

README

gate402-mcp

Public adapter plus docs for the Ogena gate402 merchant-checkout x402 API for merchants and AI agents.

  • Live API: https://api.ogenalabs.com/api/gate402 ($0.01 per checkout, verify free)
  • Demo storefront: https://api.ogenalabs.com/api/gate402/demo
  • Agent skill: docs/SKILL.md

Layout

  • adapter/ — public MCP stdio adapter (tool schemas only) for registry scoring. Execution happens on the hosted endpoint. No product logic here.
  • docs/ — explanation, skill, manifests.

Product source stays private. This repo carries schemas, skill and docs only.

Source: README.md at commit 06536a2

Tools

0
SourceWeft has not read this server's tools yet.

Version history

1
  1. v0.1.0LatestSep 16, 2026

Score

75% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts

    Declare a license in the repository or the registry entry.

Other Ogenalabs integrations