Skip to content
slashh

For developers

Give your agents company context.

A hosted MCP endpoint and a REST API for cited, permission-aware memory. Keep orchestration in your application; bring the relevant context into each request.

Connect over MCP Use the REST API

Quickstart over MCP

Three steps to a connected agent.

  1. Find your endpoint

    Your Slashh API serves MCP at /mcp. There is nothing to install. During private preview, we can help provision the environment.

  2. Create a scoped principal

    Issue an agent key through your authenticated administration flow. Limit its scopes to the workflow and keep it out of source control.

  3. Connect your MCP client

    Add the /mcp URL and the issued key to your client’s MCP configuration. The values shown here are placeholders.

.mcp.jsonJSON
{
  "mcpServers": {
    "slashh": {
      "type": "http",
      "url": "https://YOUR-SLASHH-API/mcp",
      "headers": {
        "x-api-key": "REPLACE_WITH_AGENT_KEY"
      }
    }
  }
}

The interface

Tools that speak your company’s language.

A selection of the MCP tools. Available results depend on the principal’s permissions and granted scopes.

  • Retrieve ranked context with source citations.

  • Ask a question and get a grounded answer.

  • Explore the relationships around a person or project.

  • Find people connected to a topic.

  • Retrieve decision records and their context.

  • Look up your company’s terminology.

  • Compare facts about an entity across dates.

  • Record agent-authored facts with provenance.

Use your own orchestration

Plain HTTP. The same memory.

The REST API returns the same cited, permission-trimmed answers as the MCP tools, authenticated with the same agent key.

query.tsTypeScript
const res = await fetch(`${process.env.SLASHH_API_BASE}/query`, {
  method: "POST",
  headers: {
    "content-type": "application/json",
    "x-api-key": process.env.SLASHH_AGENT_KEY!,
  },
  body: JSON.stringify({ question: "Why did we move the launch?" }),
});

const answer = await res.json();
console.log(answer.text, answer.citations);

Before the first call

Make the boundaries explicit.

  • Credentials stay server-side

    Do not embed an agent key in browser code. Store it in the execution environment and rotate it through your administration process.

  • Permissions follow the request

    Test with a narrowly scoped principal. Verify both permitted retrieval and refusal behavior before adding the tool to an autonomous workflow.

  • Inspect the evidence

    Handle missing context and ungrounded results in your application. Citations are part of the response, not optional decoration.

  • Time is part of the context

    Read tools that support as_of accept a historical timestamp. Evaluate which time boundary your workflow needs.

Build against your own questions.

Discuss a development environment, source connections and the workflow you want your agent to handle.

Discuss an integration