🧪

Created By
Azure-Samplesa year ago
APIM ❤️ AI - This repo contains experiments on Azure API Management's AI capabilities, integrating with Azure OpenAI, AI Foundry, and much more 🚀
Overview

What is AI-Gateway?

AI-Gateway is a project that explores the integration of Azure API Management with AI capabilities, including Azure OpenAI and AI Foundry, through a series of experimental labs.

How to use AI-Gateway?

To use AI-Gateway, clone the repository, set up the required prerequisites, and navigate through the available labs to experiment with various AI functionalities.

Key features of AI-Gateway?

  • Experiments with Model Context Protocol (MCP) for client authorization.
  • Integration with Azure OpenAI models and APIs.
  • Tools for managing AI budgets and costs through the FinOps Framework.
  • Various labs for testing AI functionalities like content filtering, prompt shielding, and model routing.

Use cases of AI-Gateway?

  1. Experimenting with AI models and APIs in a controlled environment.
  2. Managing AI service costs effectively.
  3. Implementing advanced AI functionalities in applications.

FAQ from AI-Gateway?

  • What prerequisites are needed to use AI-Gateway?

You need Python 3.12 or later, VS Code with Jupyter extension, an Azure subscription, and Azure CLI installed.

  • Is AI-Gateway suitable for production use?

AI-Gateway is primarily for experimentation and learning; production use should follow best practices from the Azure Well-Architected Framework.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
Azure-Samples
Star
629
Language
Jupyter Notebook
License
MIT license

Recommend Servers

View All
Tavily Mcp
@tavily-ai

JavaScript
a year ago
AI Work Market — USDC settlement rails for AI labor on Base Mainnet)
@Dario (DME)

AI Work Market is a USDC escrow protocol on Base Mainnet, designed for autonomous AI agents to find work, post jobs, and settle payments without humans in the loop. This MCP server exposes 10 tools: **Escrow lifecycle** - `create_intent_quote` — get calldata + gas estimate for funding a new escrow intent - `submit_proof_quote` — get calldata for the seller to submit a proof URI - `release_funds_quote` — get calldata for the buyer to release payment (or claim/refund) **x402 single-call binding** - `x402_consume` — replaces the 5-step x402 flow with one HMAC-signed POST that returns a delivery URL **Onboarding & discovery** - `agent_onboard` — generate a signed agent card with marketplace attestation - `agent_search` — tf-idf search over the live agent catalog - `agent_reputation` — server-side reputation from on-chain Released/Refunded/Disputed events **Live state** - `system_status` — live on-chain state (nextIntentId, accumulatedFees, contract balance, owner) - `escrow_rules` — contract semantics, lifecycle, call guides, failure modes - `events_subscribe` — SSE stream of new on-chain intent events All endpoints are serverless (Vercel) and return their schema on GET. No browser, no wallet UI required for an agent to integrate. The protocol takes a 1% commission on every settlement; the rest goes to the seller. The full AgentCard is at `/.well-known/agent-card.json` (A2A-compatible). The OpenAPI 3.0.3 spec is at `/.well-known/openapi.json` with `components.securitySchemes` (none, hmacX402). `robots.txt` allows GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Amazonbot.

6 hours ago