globalbr.ai valid

Agent setup · OpenChat + Unlinked

Use the shared Ideaflow connection hub for one connector across OpenChat, Unlinked, and Notestream Vision. Manual API-key setup remains available below.

Their llms.txt

The beginning of the file, from our validated copy saved 2026-10-27T12:30:55.077Z. Cached copy · Source on globalbr.ai

# Agent setup · OpenChat + Unlinked

Use the [shared Ideaflow connection hub](https://id.ideaflow.app/agents) for one connector across OpenChat, Unlinked, and Notestream Vision. Manual API-key setup remains available below.

Reference guides: [conversation Context and Stream](/agents/conversation-content) · [one Ask/Offer intention lifecycle](/agents/context-intentions) · [Context webhook setup and receiver verification](/agents/context-webhooks) · [agents in Context: real examples](/agents/context-stories). Lifecycle changes, private-sharing approval, and webhook setup require the owner’s direct signed-in session; connector scopes do not authorize those actions.

One Ideaflow account connects your conversations and professional network.
Start here for API keys, MCP, agent instructions, and troubleshooting.

| What you need | Connection | Docs |
|---|---|---|
| OpenChat messages and conversation context | One OpenChat API key (`oc_…`) for both REST and MCP | [API reference](/api/docs) · [OpenAPI](/api/openapi.json) · [Agent brief](/AGENTS.md) |
| Unlinked people and network search | Sign in through Unlinked MCP, or use its account grant | [Unlinked agent setup](https://www.unlinked.ai/agents) · [Agent brief](https://www.unlinked.ai/AGENTS.md) · [API schema](https://www.unlinked.ai/openapi.json) |

The apps share your Ideaflow identity and inbox. Their agent credentials are
currently separate: an OpenChat key works for OpenChat messages **and Context**;
it is not an Unlinked grant. Unlinked grants do not send OpenChat messages.

## Get a fresh OpenChat API key

Open [OpenChat](/app/) → **Settings → Agent keys → New API key**. Name the key
for the agent (for example, Hermes), then choose **Create key**. Read and write
access lets it read conversations and post messages or context as you.

**Copy agent setup** in Settings creates a new read/write key every time and
copies instructions for an agent that can make HTTPS requests. Existing keys
keep working until revoked or expired. Open an existing key to use **Copy API key**, **Copy setup with this key**,
**View full key**, or **Copy curl snippet** repeatedly. These reuse that key;
only New API key and the Settings quick setup create a new one. A new key is not required for Context.

Key management requires your signed-in user session; an agent key cannot mint
or revoke other keys.

## Connect and verify

For Hermes or another agent with HTTP tools, paste **Copy agent setup** into it.
First make this read-only call with your key:

```bash
curl -H "Authorization: Bearer $OPENCHAT_API_KEY" \
  https://chat.ideaflow.app/api/chat/conversations
```

The response is a **JSON array**, not `{ "conversations": [...] }`.
Each item has `id`, `type`, `title` (which may be null), `lastMessagePreview`,
and `participants: [{ "role": "member", "user": { "id": "…", "name": "…" } }]`.
Use `participants[].user.name` to identify a DM. If names repeat, use the ID and
recent message preview to select the intended conversat
…

Related sites

Explore similar publishers →

Similar publisher descriptions and documentation. Similarity does not imply affiliation or equivalent capabilities.

Machine-readable: GET /v1/resolve?q=globalbr.ai · GET /v1/domain/globalbr.ai · this page as Accept: application/json or text/markdown · MCP lookup_domain

Automatically discovered from public files. Inclusion does not imply endorsement or publisher participation.

Claim my listing on Agent Web Map for globalbr.ai:
1. POST https://agentwebmap.com/v1/sites/globalbr.ai/claims and keep claim_id and claim_secret private.
2. Publish the verification line "AgentWebMap verification: <token>" (token from step 1) in https://globalbr.ai/llms.txt, or use the DNS, meta-tag or well-known method the response describes. This only verifies the listing; your website and domain remain yours.
3. POST https://agentwebmap.com/v1/sites/globalbr.ai/verify with {"claim_id": "...", "claim_secret": "..."}.
4. Save the api_key from the answer; it manages the listing (PATCH https://agentwebmap.com/v1/sites/globalbr.ai).
MCP equivalent: tools begin_ownership_claim, then verify_domain, at https://agentwebmap.com/mcp. Docs: https://agentwebmap.com/docs#verify

Corrections or removal requests: contact the directory.