Connect your AI to the fund.

What this is

New Era exposes a single externally reachable door: a JSON-RPC 2.0 MCP endpoint at POST /mcp. You connect your own AI client (BYOK — bring your own key), pick the councils that match your work, and your AI calls their tools. Each call returns the fund's institutional method — the framework, the stop-the-line gates, what "good" looks like, the exact output shape — applied as a lens to the task you pass in. Your AI then produces the finished work using your data, on your side. The fund runs no LLM of its own and never stores your inputs; a mandatory outbound filter strips any sensitive detail before anything crosses the connection.

Quick start

From zero to your first institutional answer in four steps.

1. Register & generate an API key

   Enter your room (the home page is your sign-in — a magic link arrives by email), then click generate key under "Connect your AI". The key is shown once — copy it immediately. It looks like neif_… and travels as a Bearer token. The gateway only ever stores a hash of it, so a lost key is rotated, never recovered.

   Access is admin-approved. You can register, choose a package and prepare your setup right away, but the MCP gateway and your API key activate once an administrator approves your account. You'll be notified when access goes live.

2. Add the MCP server to your AI client

   In your MCP-capable client (Claude Desktop, or any other), open Settings → Developer → Edit Config and paste this block. Swap in your own key:

   claude_desktop_config.json

   {
     "mcpServers": {
       "newera": {
         "url": "https://neifcapital.com/mcp",
         "headers": {
           "Authorization": "Bearer YOUR_KEY"
         }
       }
     }
   }

   The endpoint is https://neifcapital.com/mcp — paste that as the URL and your approved key as the Bearer token. Restart your client after saving.

3. Your AI discovers the tools

   On connect, your client calls initialize and then tools/list. The gateway returns the always-on public tools, plus the tools of every council in your package, plus your private-KB tools if your package includes the hosted KB — and nothing else. Each tool's description includes its credit cost.

4. Ask a question that matches a wired council

   Describe your task in plain language; your AI picks the right tool and calls it via tools/call. Start with something the public corpus answers (search_knowledge), or — once you've wired a council — paste a real brief and ask for the method (e.g. eval.full for a full company evaluation, quant.var for portfolio risk).

The tools

A narrow, metered, audited surface. Read / analyse-only. No tool reads another tenant's private data.

Public tools — always on

These three are available to every account and read only the fund's published, public corpus.

Council tools — council.method

Every council you own exposes its own tools, named council.method. A few examples across the bench:

Each council tool takes a single input — free text: your task plus the data the council needs to work on. Be concrete: paste the figures, statements or brief, or describe the company, deal, portfolio or question. The tool returns the fund's institutional method for that task — your own AI then applies it to your data. The fund runs no LLM and stores nothing; you get the framework and structure back, your AI does the synthesis.

{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "eval.full",
    "arguments": {
      "input": "Evaluate Acme Co. for acquisition. Revenue 42M USD, EBITDA 7M, ..."
    }
  }
}

The complete catalogue — every council, its tools and their per-call credit costs — is on the Packages page and inside your room. Which councils you can reach is set by your package (Core, Advanced or All-Included); a tool only appears in your tools/list if your package includes it. Calling one outside your package is not an error — it returns a short note pointing you to the package that includes that council.

Knowledge base

Public corpus for everyone · your private KB stays yours.

There are two knowledge layers, and they never mix:

The public corpus is read-only to everyone, reached through search_knowledge / get_knowledge / list_topics. It exposes only rows marked public, from a table with no client columns.

Your private KB is per-tenant and fully isolated — scoped to your account, never shared, never blended with the public corpus or another tenant. If your package includes the hosted KB, two extra tools appear:

Set your jurisdiction

The model is worldwide and assumes no country — until you tell it yours.

New Era is jurisdiction-neutral by design. To ground every council in your market, run the jurisdiction.setup tool once (just ask your AI: "set my jurisdiction"). It walks a short questionnaire — your regulator, currency, registries, accounting standard and tax — and your AI saves the resulting profile into your own knowledge base. After that, every council grounds its analysis in that profile.

Usage & credits

Metered in credits, per call. You only draw for what runs.

Usage is metered in credits, drawn per call. Every tool shows its credit cost up front (in this page's tables and in each tool's description via tools/list). You hold a credit balance; each metered call runs inside a credit escrow — if your balance can't cover the cost, the call is refused and nothing is returned or charged, and a failed call is refunded. Every metered call (ok, denied or insufficient) is written to an auditable ledger, so you can reconcile exactly what ran.

Which councils and tools you can reach is set by your package — see the Packages page for what each one includes.

Errors

Standard JSON-RPC 2.0 error objects: { "jsonrpc": "2.0", "id": …, "error": { "code": …, "message": … } }

FAQ