Skip to main content
Glama
306,652 tools. Last updated 2026-07-25 18:37

"Connecting to an External API for Agent-Based Replies" matching MCP tools:

  • Get information about the organization your agent is linked to. WHEN TO USE - You want to know which organization your agent is operating under. - You need to list the members of your linked org (e.g., to decide which member should review a deliverable). WHEN NOT TO USE - To create, update, or delete organizations — those actions require human authentication via the REST API (POST /api/v1/organizations, PATCH /api/v1/organizations/{slug}, etc.). BEHAVIOR - Read-only. Auth required: agent API key. Rate-limited to 60 req/min. - Returns an error if your agent is not linked to any organization (agents.org_id IS NULL). - action='get_my_org': returns org name, slug, tier, owner, and member count. - action='list_members': returns human_id and role for each member. WORKFLOW - Check your org membership before referencing org context in deliverables or communications. - To link your agent to an org, a human admin must call POST /api/v1/organizations/{slug}/agents.
    Connector
  • Post a new comment on any target in a workspace: a row, a cell, a doc text range, an html element, an entire surface, or the workspace itself. Polymorphic target shape mirrors the REST POST /api/workspaces/:slug/comments. For threading, pass `parentId` to hang the new comment as a reply (the server flattens nested replies to single depth and auto-unresolves a resolved parent). Mentions are an array of `{ kind: 'user'|'agent', id, label }` triples; the server validates each mention's access to the workspace before accepting. Fires `comment.added` (and `comment.unresolved` when a reply reopens a resolved parent). For replies to existing comments where you don't want to reconstruct the target, prefer `reply_to_comment` which derives the target from the parent. Editor or commenter role required.
    Connector
  • Probes a domain for known AI agent integration signals: `llms.txt`, `ai.txt`, `/.well-known/ai-plugin.json`, `openapi.json`, `swagger.json`, MCP manifest, MCP SSE endpoint. Returns a score based on the count of signals detected. Use this to assess whether a domain is ready for agent-to-agent interaction. Use this tool when: - You want to know whether a domain exposes an MCP server or OpenAPI spec for agents. - You are cataloguing the AI-agent-ready surface of a set of domains. - You need to decide whether to attempt programmatic API access to a domain. Do NOT use this tool when: - You need tracker/surveillance data about the domain — use `get_domain` instead. - You need the robots.txt AI crawler policy — use `intel_robots` instead. - You need HTTP security posture — use `intel_http` instead. Inputs: - `domain` (query, required): Domain to probe. Returns: - Boolean flags per signal (`llms_txt`, `ai_plugin`, `openapi`, `mcp_manifest`, `mcp_endpoint`, `mcp_sse`). - `agent_surface_score`: integer 0-8, count of signals detected. Cost: - Free. No API key required. Latency: - Typical: 2-5s (parallel probes), p99: 8s.
    Connector
  • Use this when a ChatGPT user wants to see what Influship can return before linking an account. Fetches one configured sample creator with social profile context. This is a low-cost preview tool and should not be used for search, discovery, matching, or lookalike requests. After showing the preview, tell the user that real live creator data, search, lookalikes, matching, posts, and transcripts require connecting an Influship account. Explain that they can authorize either an Influship SaaS subscription, where usage counts against monthly bundled credits, or an Influship API account, where usage is billed pay-as-you-go under API billing.
    Connector
  • Find the best paid x402 API for a data capability across discovery sources (Apiosk catalog + federated external listings). Decompose the user's request into capability segments first, then call this once per capability. Returns a normalized, ranked list; each result's `executable_via` says whether to call apiosk_execute (Apiosk-settled) or apiosk_inspect_x402 + apiosk_fetch_paid (external). Use this instead of apiosk_search when the goal is 'get real paid data for X', not just browsing.
    Connector
  • Find the best paid x402 API for a data capability across discovery sources (Apiosk catalog + federated external listings). Decompose the user's request into capability segments first, then call this once per capability. Returns a normalized, ranked list; each result's `executable_via` says whether to call apiosk_execute (Apiosk-settled) or apiosk_inspect_x402 + apiosk_fetch_paid (external). Use this instead of apiosk_search when the goal is 'get real paid data for X', not just browsing.
    Connector

Matching MCP Servers

Matching MCP Connectors

  • Connect any two AI agents and let them talk directly. Claude to Claude, Claude to OpenAI, or any MCP-compatible agent

  • x402 pay-per-call tools: company enrichment, PDF extraction, Amazon/KDP data, YouTube transcripts.

  • 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")
    Connector
  • Get a personalized market news briefing based on your validated edge library. Profiles your strategies, searches today's news for the instruments and setups you actually trade, and writes a concise digest connecting each headline to your specific book. Each news item includes a ↳ line tying it to your actual positions and edges (e.g. 'your ES momentum setups', 'your GC mean-reversion edge'). Requires at least 5 strong edges in your library. Costs credits.
    Connector
  • Register a new agent account and get an API key. No authentication needed. The returned API key grants read+write access to all BorealHost API endpoints. Store it securely — it cannot be retrieved again. The key is automatically activated for this session — all subsequent tool calls will use it. No extra configuration needed. If no email is provided, a synthetic agent identity is created (agent-{uuid}@api.borealhost.ai). If an email is provided, it links to an existing or new human account. Args: name: Human-readable name for this API key (default: "Agent Key") email: Optional email to link to a human account Returns: {"api_key": "bh_...", "key_id": "uuid", "prefix": "bh_...", "scopes": ["read", "write"], "account_id": "uuid", "message": "Store this API key securely..."} Errors: RATE_LIMITED: Max 5 registrations per IP per hour VALIDATION_ERROR: Invalid email format
    Connector
  • SANDBOX/ONBOARDING ONLY: request the capped trial sandbox faucet for test CPTM (one grant per agent per 24h). Credits the managed Conductor Relay DB balance only — not connected to any chain or external wallet, and no external withdrawal. This is NOT agent earnings and NOT Agent Treasury / Catalog earned commission (earned commission = verified conversion → Treasury finalization → internal DB-CPTM exchange credit). Bearer token required. See /agents/cptm-policy.
    Connector
  • Use this before selecting, delegating to, or recommending the AIノアカリ☆ Result Receipt Auditor. It rechecks the canonical Agent Card, external A2A conformance, health and uptime, two registries, a signed NANDA development attestation, ServerHub state, and deduplicated external execution receipts. It explicitly separates external verification from organic adoption, purchase intent, cash, human outcome, and production identity. No authentication, payment, personal data, or request arguments are required.
    Connector
  • List every registered Trillboards API operation. WHEN TO USE: - First call in an agent session to learn what the API offers. - Filter to agent_safe=true to list only side-effect-free endpoints. - Narrow to a single surface (data-api, sdk-api, device-api, sensing-api, partner-api-generated, dsp-api-generated). RETURNS: - operations: Array of { surface, method, path, operation_id, summary, description, agent_safe, idempotent, cost_tier, tags, doc_url, example_request } - total_operations: Total count. - surfaces: Known surface identifiers. EXAMPLE: Agent: "What read-only endpoints can I call?" list_endpoints({ agent_safe: true })
    Connector
  • Create a deterministic, read-only pre-action receipt from request, policy, and optional result evidence. Use before an agent posts, spends, lists, or writes so the decision can be audited; no external action is executed.
    Connector
  • Return service health, supported chains, OFAC list refresh timestamp + size. Pure introspection — no external API calls, no money handling. Returns: dict with `status`, `supportedChains`, `version`, and (when the OFAC list is loaded) an `ofac_list` block with `updated_at` + `sdn_count`.
    Connector
  • Start a browser-based sign-in flow to get an API key for full access. Call this when you need detailed analysis results (reasoning, measurements) that require authentication. Returns a verification URL to show to the user. After the user signs in, poll check_device_auth with the returned user_code to get the API key. Returns: { "verification_url": str, "user_code": str, "expires_in": 600, "message": str }
    Connector
  • Permanently revoke an agent: its API keys stop authenticating immediately (incident response). Irreversible. Issue a new agent to restore access. Its audit history is kept. Requires the `agents:write` scope. Prefer `axiorank_quarantine_agent` for a reversible pause.
    Connector
  • List the calling customer account's OWN message conversations with businesses, newest first, each including the business's replies — the read half of send_message_request, so an agent can report answers back to its user. Follow pagination.next_cursor until pagination.has_more=false to traverse older history. Pass conversation_id from a webhook resource for one exact scoped lookup; conversation_id and cursor are mutually exclusive. Requires a valid scoped agent API key whose account_id matches the account_id argument (call get_agent_identity first); keys scoped to send_message_request may also read. Read-only: never modifies anything.
    Connector
  • Create an agent-scoped API key (chr_ak_*) that can only act on behalf of a single agent. Use this to self-provision or rotate per-agent credentials. The plaintext key is returned exactly once in the response — store it immediately, it cannot be retrieved later. Requires an org-level API key.
    Connector
  • Edit a previously generated video with a text prompt and optional reference images (video-to-video). Pass the video `url` you received from `createVideo`, `createVideoFromReferences`, or an earlier edit — it must be a video you generated within the last 7 days; arbitrary external videos are not accepted. Optionally add up to 5 reference `images` (URL or base64) to guide the edit. Synchronous: the call blocks until rendering finishes and returns the new video URL and its actual duration in seconds. Credits are charged only on success, based on the produced duration and never more than the duration you requested. Pass an optional `request_id` to tag the result so you can locate it later via `getVideoResults`. Related tools: `createVideo` to generate the source clip, `createVideoFromReferences` for reference-driven generation. Requires an API key (user scope). Credits: cost varies by model and duration (credits/sec): Eagle 2/s; see this endpoint's full pricing table in the API docs.
    Connector