Skip to content

Connect to Ariquo

Query curated events, briefings and reports from your application or agent. Follow each finding back to its original source.

Beta · Key required

Choose a connection

One connection. Three tools.

Add this connection in a client that supports remote MCP with Bearer authentication. No local Ariquo service is needed.

Server URL

https://your-ariquo-domain.example/api/mcp
Transport
Streamable HTTP
Scope
data:read
Connection parameters
{
  "url": "https://your-ariquo-domain.example/api/mcp",
  "transport": "streamable-http",
  "headers": {
    "Authorization": "Bearer <ARIQUO_API_KEY>"
  }
}

Adapt these fields to your client’s format and replace the key placeholder. This is not a universal client config. Automatic OAuth registration is not supported yet.

Connected? Try a question.

Let your agent choose the tools, then check the sources in its answer.

Find published technology events about API pricing. Include the original sources.

List the latest security briefings, then read the most recent edition.

What you can query

Search events

Find events by domain and keyword, with summaries and original sources.

ariquo_search_events

Browse editions

List published news editions, daily briefings, reports and deep dives.

ariquo_list_publications

Read an edition

Retrieve a complete edition and its source evidence by publication ID.

ariquo_get_publication

Before you connect

Why is a key required?

API and MCP use a separate data:read permission to control access and request frequency. Keep keys in private configuration or a secret store, out of URLs, chats and public code.

Can I use a skill with this?

Yes. Connect MCP first, then have your agent query by domain, verify the original articles and cite sources. A skill organizes those steps; it uses the same connection and permissions.

What if the connection fails?

401: check for an invalid or expired key. 403: check the data:read permission. 429: wait as instructed by Retry-After. A 404 can mean the operator has not enabled the service. Your client needs remote HTTP and Bearer-header support. Never include your key in a support message.

Can I redistribute the content?

API access does not include permission to resell full text or commercially redistribute content. Content licensing must be agreed separately.