AI Use Cases Hub

Research real AI deployments from your agent.

Four MCP tools bring source-linked enterprise AI research into your workflow. Start with up to three abbreviated results per search, without registration or an API key.

A real preview result

Search: “insurance claims” · Captured

Legal-i: medical insurance claims

Insurance · Switzerland · Azure OpenAI

Azure OpenAI helps organize insurance documents and streamline claims work with Baloise.

Microsoft customer story (now named amaise)

Abbreviated from a returned record. Results vary with your query and the available corpus.

Connect your agent

A free account includes 100 monthly credits for personal API and MCP access. Browsing deployments in the app does not consume personal credits. View allowances

Choose your client, copy its setup, then ask your first research question.

Add this entry to ~/.cursor/mcp.json. If the file already has servers, merge the AIUseCaseHub entry into it.

No registration or API key is needed. The preview returns up to 3 abbreviated results per search.

Reload Cursor and enable the AIUseCaseHub tools in your agent.

Cursor setup documentation

Cursor · free preview
{
  "mcpServers": {
    "aiusecasehub": {
      "url": "https://basic-backend713-dsd8hygyfkc8d8f5.swedencentral-01.azurewebsites.net/api/mcp"
    }
  }
}

Ask your first question

Use AIUseCaseHub to find three examples of AI in insurance claims. Summarize what each deployment does and link to its original source.

Allow the tool call when your client asks. A successful search returns source links; the agent can use a detail lookup to explore a result.

Start free. Expand when you need more.

Public MCP preview and personal API-key access compared
AccessFree previewPersonal API key
Getting startedNo registrationAccount and API key
Results per searchUp to 3Up to 20
Case detailsAbbreviated, source-linked recordsFull available case details and analysis
Account credits02 per search · 1 per detail lookup

The preview allows 10 tool-call attempts per IP per UTC hour, with a shared service limit of 200 per hour. Discovery and tool listing are free of that allowance. Personal keys are charged only for successful calls.

Four tools for your research

Find relevant deployments

Start here: search enterprise AI deployments in plain language.

search_usecases

Narrow your research

Combine a natural-language query with supported filters.

hybrid_search_usecases

Discover similar ideas

Find related implementations even when they use different words.

vector_search_usecases

Look into a case

Retrieve one search result by its row key. Full access adds the detailed record.

get_usecase_details

Full tool and endpoint reference

Protocol, limits and troubleshooting

The endpoint uses Streamable HTTP over POST, supports protocol 2026-07-28 and older initialization-handshake clients, and does not issue a Mcp-Session-Id.

A tools/call response contains MCP content. Parse the first text item as JSON. The current protocol also returns resultType: complete. Search payloads include items, total, searchMode, dataSnapshot and _mcp credit metadata.

Preview descriptions are capped at 360 characters. Full analysis and detailed outcome fields require a personal key. The limit argument accepts 1–20; anonymous searches are capped at 3.

If a preview is rate-limited, follow the returned retry guidance. If a key is invalid, empty or revoked, remove its header to return to the preview, or replace it with a valid key. Keys are shown once when generated on the API page.

In Microsoft Foundry, choose no authentication for the preview, or key-based authentication with the X-API-Key header for full access.

For a scripted connection check, use the verifier in the GitHub setup examples.