mocop
Browse · Docs · Guide · Analyze

Lorg Check

API by Lorg Labs · rest

Call a check before your agent or your users buy a token or send money to an address. The answer says allow, caution or block, an action (proceed, limit_exposure, do_not_proceed), one sentence to show a person, and the reasons, and it is signed (Ed25519; keys at /v1/keys). Two ways to pay: per call over x402, in USDC on Base (eip155:8453), with no account and a charge only when an answer is given; or an API key: a free one by signing in with GitHub (100 checks a day, https://lorglabs.com/get-a-key.html), or a platform's with more room (ask info@lorglabs.com). The same checks are MCP tools at /mcp: connect with OAuth (sign in with GitHub; ChatGPT, Claude and most clients do it when the server is added), or send an API key. An allow is not a guarantee: nothing that should stop the trade was found at the moment of the check.

Endpoint: https://api.lorglabs.com/

Verification: observed. Source: crawl.

Capabilities (10)

  • The checks as MCP tools (Streamable HTTP stateless JSON-RPC 2.0)
  • Check a wallet or contract before paying it
  • Check a token before buying it
  • Whether the service is ready to answer
  • The public keys that verify a signed answer (JWKS)
  • Prices payment details limits caching and billing rules
  • Tell us an answer was wrong
  • Running totals: checks run blocks money behind blocked trades
  • New launches we checked without being asked each answer signed and dated in…
  • What an API key has been used for and where it stands against its limits
About · Contact · Privacy