AskTheApi Team Builder

Created By
AlexAlbalaa year ago
Agent network builder for communicating with openapi apis. Based in autogen
Overview

What is AskTheApi Team Builder?

AskTheApi Team Builder is a high-level Python library designed for building and managing networks of autonomous agents that collaborate to solve complex tasks, specifically tailored for APIs defined using the OpenAPI standard.

How to use AskTheApi Team Builder?

To use the library, install it via pip and create agents from an OpenAPI specification. You can then build and run a team of agents to perform tasks collaboratively.

Key features of AskTheApi Team Builder?

  • Effortless agent network creation based on OpenAPI specifications.
  • Team-based collaboration with automatic coordination.
  • Real-time streaming interactions among agents.
  • Built-in HTTP client for external API calls.
  • Type safety with Pydantic for robust data validation.
  • Clean and intuitive API for developers.

Use cases of AskTheApi Team Builder?

  1. Automating API interactions with multiple agents.
  2. Building complex workflows that require collaboration between agents.
  3. Creating dynamic applications that respond to real-time data.

FAQ from AskTheApi Team Builder?

  • Can I use this library with any OpenAPI specification?

Yes! The library is designed to work with any OpenAPI-compliant API.

  • Is there a cost associated with using AskTheApi Team Builder?

No, it is open-source and free to use under the MIT License.

  • How can I contribute to the project?

Contributions are welcome! You can fork the repository and submit a pull request.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
AlexAlbala
Star
0
Language
Python
License
MIT license
Tags

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago