Skip to main content
Glama
777,931 tools. Updated 2026-11-13 19:20

"How to obtain an API key" matching MCP tools:

  • Generate a new API key for your agent. The full plaintext key (m2m_...) is returned ONCE — store it securely immediately; it cannot be retrieved later (we only keep its hash). Use keyName to identify the key's purpose (e.g. 'production', 'staging'). Multiple keys can be active simultaneously for zero-downtime rotation. Requires: an existing API key from register_agent. Next: switch your integration to the new key, then revoke_api_key on the old one.
    ConnectorNo auth
  • Create a free personal PropLine API key for the user and EMAIL it to them. Use this when the user wants their own key — e.g. they hit a shared-demo-key rate limit, a paid field came back redacted, or they ask how to get a key. Only call it with an email address the user explicitly gave you for this purpose in this conversation; never guess, reuse one from elsewhere, or sign up a third party. The key is never returned here — it goes to that inbox, with instructions to reconnect this assistant using it. Free tier: 1,000 requests/day, no card. If the address already has a key, the key is re-sent (at most once a day).
    ConnectorNo auth
  • Creates and immediately sends an external project inquiry to a private Relux Works Telegram chat for human review. Do not call it to test the connector or demonstrate MCP. Build the summary from known conversation context, ask only for missing details, obtain a real user-provided or user-confirmed reply route to the decision maker or an accountable relay agent, and show the complete draft including that route. Before calling, provide https://relux.works/en/privacy-policy/ and obtain explicit user consent. Never invent or infer contact details. The current MCP chat is not a reply route. A human replies within one business day with a recommended package and a fixed-price quote.
    Connector
    Destructive
    No auth
  • Get a new API key for an existing Disco account. Sends a 6-digit verification code to the email address. Call discovery_login_verify with the code to receive a new API key. Use this when you need an API key for an account that already exists (e.g. the key was lost or this is a new agent session). Returns 404 if no account exists with this email — use discovery_signup instead. Args: email: Email address of the existing account.
    ConnectorNo auth
  • Permanently deactivate an API key by its database ID. Requests using the revoked key are rejected immediately. Use this after rotating to a new key via create_api_key. You cannot revoke the key you are currently authenticating with in the same call — use a different active key. Requires: API key from register_agent.
    Connector
    Destructive
    No auth
  • Step 1 of autonomous self-registration - no API key required. Costs $0.01 USDC on Base (anti-spam fee, not a wallet-ownership proof). Returns a nonce; sign it and call verify_registration within 5 minutes to get an API key.
    ConnectorNo auth

Matching MCP Servers

Matching MCP Connectors

  • Check whether a Vivideo API key is present on this request. Call this FIRST. Returns { configured: boolean }. If false, ask the user to add an Authorization: Bearer vv_live_... header to the MCP server config (a key from https://app.vivideo.ai/account/api-keys). Never asks for or exposes the key.
    ConnectorNo auth
  • Summarize the user's imported collection: how many distinct cards, total copies, and where it was imported from. This is the SUMMARY only. Use search_my_collection to look up individual owned cards, and what_can_i_build to rank commanders they could assemble. Requires a free API key (send it as "X-API-Key: <key>" or "Authorization: Bearer <key>").
    ConnectorNo auth
  • Show what this connection may use. With an API key: your current plan, remaining allowance, which model_versions and speaker ids you may render. Without a key: the purchasable plan ladder and how to get a key. Free, no credits consumed. Call this FIRST when any tool returns a 401 or 403 — it is the fastest way to learn what went wrong.
    ConnectorNo auth
  • Revoke an API key permanently. The key will immediately stop working. You must own the key. Use list_api_keys to find the key ID.
    Connector
    Destructive
    No auth
  • Create a Stripe Checkout link to buy a credit pack (see list_credit_packs). A human must open the link and pay; this tool charges nothing. With an API key, the credits go to that key. Without a key, a new key is created after payment: call claim_api_key with the returned session_id to receive it (once).
    ConnectorNo auth
  • Run an existing activated pipeline, capped at row_limit. Two steps: without confirmation this only returns the row allowance and maximum charge estimate and runs nothing. Show it to the user; after they agree, call again with the same arguments plus the returned confirmation to start the run, then inspect it with get_run. Approval binds the selected revision and retry key; if the active revision changes before confirmation, obtain a fresh estimate and approval. Reads the pipeline's web sources and never posts to them; notifications the user already configured in Jsonify may fire when it finishes. Does not author code or change schedules. Reuse the exact key and arguments on retry.
    ConnectorOAuth
  • Create a new API key in one of your workspaces. Requires admin access in that workspace. The plaintext key is shown exactly once in the response. It is never retrievable again after this call, so save it immediately. Not available when this MCP connection is itself authenticated with an API key (headless mode): a leaked agent key must not be able to mint more keys. Mint keys from an interactive (OAuth) session or the console instead. workspace: optional workspace id, workspace name, or `org-name/workspace-name` when the same name occurs in two of your orgs (defaults to your default; use list_workspaces to discover them). name: a label for the key, shown in the workspace's key list later. scopes: key capabilities: ["ingest"] (default) to send telemetry, add "read" (["ingest", "read"] or ["read"]) for a key that can also be used as the Authorization bearer for headless MCP connections. The alert-management capabilities (alerts:manage, channels:manage) are deliberately NOT mintable here — an admin issues those in the console, because a key minted by an agent never expires by default and would be an unbounded credential to leak. Example: > Create an API key so this agent can send traces. ```json { "name": "create_api_key", "arguments": { "name": "my-agent" } } ``` > Give it a key that can also read traces over MCP. ```json { "name": "create_api_key", "arguments": { "scopes": ["ingest", "read"] } } ```
    ConnectorAPI key
  • Get setup info for Rudow's client SDKs (Node.js backend, Python backend) — package name, install command, a minimal config/usage snippet, and how to obtain a project ingest API key. Use this to help a user add logging to their own codebase: install the right package for their stack and write the snippet into their code yourself — this tool only returns information, it does not install anything or touch the user's files. It never creates or reveals an ingest API key; the user must generate one manually from the dashboard (see key_instructions in the result) and paste it in themselves.
    ConnectorAPI key
  • Returns change points this service recorded over time for an endpoint (e.g. exchange rates, weather) as compact CSV. Use the same params as the live call. When to use: to see how a live value (e.g. an exchange rate or the weather at a place) changed since this service started recording it. For long official histories use get_series instead. Returns an error if nothing was recorded for these params. Read-only, no API key or signup. Free quota: 1000 calls/day per IP, shared across tools.
    ConnectorNo auth
  • Buy 30 days of Pro (unlimited premium calls) for $29 in USDC, paid over x402 on Base. Without an X-API-Key it issues a new Pro key; with one it renews that key (a free key is upgraded in place), adding 30 days to its current end. The first call answers with the payment requirements; pay and retry with the X-PAYMENT header. The payment is taken only once the key is ready. No automatic refunds. If the answer says the payment could not be confirmed, do not pay again: quote its reference. How to pay: https://github.com/johnsmithxy1mmm-sys/HyperliquidMCP#pricing
    ConnectorNo auth
  • Create a new API key for the current organization and return its raw_key value exactly once — it is never shown again, so store it immediately. expires_at optionally sets an ISO-8601 expiry and device_limit caps how many devices the key may register (validated against the plan ceiling, invalid_device_limit on excess). Key creation is rate-limited per organization (api_key_create_rate_limited). Use list_api_keys to see existing keys and revoke_api_key to retire one.
    ConnectorNo auth
  • List the sessions open for this API key, to recover a session_id you've lost or to see how many are open before create_session. Returns {sessions: [{id, documentId, libraryFileId, createdAt, updatedAt, sheetCount, memBytes}]}, times in epoch milliseconds; closed and expired sessions are left out. Pass an id to any session tool, or to close_session to free a slot. Takes no arguments. Each API key can hold 5 open sessions, and a session closes on its own after 30 minutes without a call.
    ConnectorAPI key
  • Read the workspace's activity log, newest first: who changed what and when, and how (in the web app, with an API key, or by nopaque staff). Covers API keys, members and roles, billing, tests and their schedules, load tests, batches, sweeps, mapping jobs, imports, phone numbers and caller ID, alert rules and destinations. Filters: category (access, keys, billing, workspace, testing, numbers, assistant), action (e.g. api_key.created), actor (a user id or API key id), target (type:id, e.g. test:<id>), from/to (dates), limit (at most 100) and cursor (nextCursor from the previous page, sent with from = the previous window.from). Use cases: "who changed our API keys last week" (category keys), "who deleted that test" (target test:<id>), "what did this key do" (actor <key id>). Entries hold ids, not names: name a test with getTestConfig or getMissionTestConfig. nopaque staff show with no id. Only entries inside the plan's window (window in the response) are returned. Needs an Enterprise workspace and an API key created by an owner or admin with the audit:read scope by name; a key with full access (*) or with no scopes is refused (403), and a key made by a billing admin reads only the billing category. Every call through this server counts as a call with an API key. Read-only.
    ConnectorNo auth
  • Register as an agent to get an API key for authenticated submissions. Registration is open — no approval required. Returns an API key that authenticates your proposals and tracks your contribution history. IMPORTANT: Save the returned api_key immediately. It is shown only once and cannot be retrieved again. Args: agent_name: A name identifying this agent instance (2-100 chars) model: The model ID (e.g., "claude-opus-4-6", "gpt-4o")
    ConnectorNo auth
  • FREE (no API key needed). Use when you already have an Entia Home URL path (country/sector/city/slug) and need that public business page as data. Retrieve the Schema.org JSON-LD @graph for a specific entity's Entia Home (machine layer at /v1/identity/{country}/{sector}/{city}/{slug}.jsonld). Requires country, sector, city, slug path segments — not cif/q. Obtain the path via entity_lookup / showcase (canonical_url). Fail-closed: never returns ENTIA corporate marketing as if it were the entity.
    ConnectorNo auth