Skip to main content
Glama
714,707 tools. Updated 2026-10-29 03:19

"agent-api" matching MCP tools:

  • Manage API keys for the authenticated user. Actions: list, create, get, update, delete. API keys are used for generation endpoints (/api/v6, /api/v7, /api/v8). All actions require authentication.
    ConnectorNo auth
  • Get redacted metadata for the calling API key—ID, name, environment, scopes, and timestamps—for agent self-inspection without exposing the secret. Requires API-key auth.
    MIT
  • Retrieve structured agent profile data from a Redfin agent profile URL, including name, contact, brokerage, ratings, and recent transactions.
    MIT
  • Register a new agent with Lithtrix to obtain a one-time API key. No authentication required; agree to terms and provide agent name and owner identifier.
    MIT
  • Generate an agent API key (floe_...) to enable AI agent payments and credit. Optionally cap spending with a rolling budget; store the one-time secret securely.
    MIT
  • Revoke an agent API key to immediately block authentication for that key. Irreversible: use rotate_agent_key to keep the agent running while replacing credentials.
    MIT

Matching MCP Servers

  • F
    license
    Not graded
    quality
    D
    maintenance
    Enables automated company formation across multiple jurisdictions with REST and MCP interfaces. Supports jurisdiction listing, requirement details, cost estimation, and secure API key management.
    -
  • F
    license
    Not graded
    quality
    C
    maintenance
    Enables AI agents to submit data center colocation requirements to OCOLO, retrieve broker guidance, and check request status without an API key.
    -

Matching MCP Connectors

  • x402 or card pay-per-call: invoice JSON, DNS, whois, SSL, geocode, RSS feeds, sitemaps, QR codes

  • Japan JMA warnings, typhoons, volcano levels and municipality code history in English; x402 checks

  • Create a bc_* machine key to register an agent for Beecargo file hosting. No API key needed; the MCP session adopts the key after creation.
    MIT
  • List delegated agent keys for the authenticated wallet (address, label, expiry). Requires API credentials; use fetch_agents instead.
    Apache 2.0
  • Retrieve metadata of all active agent-scoped API keys for an organization, including ID, prefix, agent ID, label, and creation date.
    Apache 2.0
  • Learn about Proxenio's verified intent network and agent API to understand trust tiers, capabilities, and authentication before connecting.
    MIT
  • Self-register as an AI agent to receive an API key for TuringWell write operations. Store the key securely; this unauthenticated first step enables posting questions, answers, and outcomes.
    MIT
  • Read the full Lorg agent manual before contributing. Review all 5 contribution schemas, trust system rules, orientation guide, and API contract to ensure compliant participation.
    MIT
  • Create an agent-scoped API key that authorizes actions for a single agent. Returns the plaintext key once; store it immediately.
    Apache 2.0
  • Revoke an agent-scoped API key permanently by providing its ID. The key stops working within a minute.
    Apache 2.0
    Destructive
  • Launch an asynchronous catalog discovery agent to crawl data sources and refresh catalog metadata. Poll agent history to track completion.
    Apache 2.0
  • Create a new email agent account with identity, API key, and persona for automated email handling and delegation.
    MIT
  • Register a Yolfi workspace to obtain an API key when none exists. Provide agent and project name to create the workspace and retrieve the key.
    MIT