How can we help?

In the app, at /auth/register: email and password, or Google. The activation arrives by email; once confirmed, the dashboard opens.

Nothing. The free plan covers one project, asks for no card and does not expire. The paid steps have their prices published at /pricing: Solo US$20, Núcleo US$99, Operação US$249 — contracting starts in a conversation.

Claude Code, Cursor, Kiro CLI, Hermes Agent, OpenClaw and any MCP-compatible client. Per-agent setup guides live in the docs.

Minutes: create the account, mint the MCP token in the dashboard, paste the config into the agent. From then on, hooks start capturing from the first session.

Model Context Protocol, the open protocol LLMs use to reach external sources and tools. ValorBrain runs an MCP server at mcpbrain.valor.digital, with OAuth 2.1 and dynamic client registration.

MCP token. It connects the agent to the MCP endpoint and also works on the engine's REST routes, with the same scopes. The dashboard API key exists for one case: pushing a document over HTTP to the ingest route.

Yes, and that is the point of the product: a decision captured in Claude Code shows up for Cursor in the next session. The memory is the same for people and agents.

In the dashboard, under MCP token settings: revoking the token cuts access immediately (the permission cache expires in under a minute).

More than 90 in the current catalog, between canonical tools and aliases, each with a REST mirror. The catalog ships with a parity test against the code.

Through hooks in the cycle of the agents the team already uses: capture happens during the work, with no new screen to open. Whatever needs human validation gets flagged for review.

No. The previous version is superseded, with a validity window. Conflicts between sources get detected and quarantined until a person approves or rejects them.

Yes. Every call runs inside the tenant context (row-level security), and the agent sees what the person using it can see. With source ACL enabled (tenant opt-in), collections from sensitive domains get restricted per person, role or agent, with validity and reason recorded on the grant.

Yes: every answer lists the origin document, the date and the collection. When the evidence does not exist, the agent says it found nothing instead of improvising.

Every mutation records actor, action and before/after state in an append-only trail with a hash chain: editing a row breaks the chain. Read logging with identity and version is in development.

One project, one person, 1,000 documents, unlimited memory searches and 50 sourced answers per month. Enough to prove the product on your real flow.

Documents and searches: no quota, no meter. There is a fair-use storage ceiling that in practice equals over a hundred thousand documents; it exists for the pathological case, not the normal customer.

Per plan and per people: Solo, Núcleo and Operação have a monthly price published at /pricing, with an extra seat at a fixed price. Nothing is billed per response or per document; agents take no seat and searching costs nothing. On the annual cycle you pay 10 months and use 12.

Yes. Full JSON export from the dashboard or the API. It is a data-subject right under the LGPD and does not depend on the plan.

Access continues until the end of the paid period; then the account drops to the free tier and your documents stay where they are. Account deletion erases everything within 30 days, backups included.

On our own hardware in Santa Catarina, Brazil. Multi-tenant Postgres with row-level isolation; embeddings and reranking run on the same machine's GPU. Self-host and dedicated instances under enterprise contract.

The engine does not touch your sources: the connectors live in the SaaS. No outbound call leaves the engine to fetch third-party content on its own.

We hold no SOC 2 certification and promise no date. What the security page marks as verified has evidence in code and production configuration; anything unverified shows up as in preparation.

Yes, published on this site, with the data received, the purpose and the location of each third party, including the inference step that leaves the country.

The token expired or was revoked. Mint a new one in the dashboard and update the agent's config (for Claude Code, ~/.claude.json).

Check in the dashboard whether documents were indexed (collections and counters). Try keyword mode if auto mode fails. If documents are pending embedding, nudge the worker.

Check spam and promotions, add [email protected] to your contacts, and use the resend option on the login screen. If it persists, write to us.

The status page shows real availability for the engine and the SaaS. To report, send email with a timestamp and the error message.