Same response structure
SDK, HTTP, and MCP return the same grounded answer and supporting records.
Build with current source data.
Give any agent or application a grounded answer from current data through an SDK, HTTP, or MCP. Keep data ready or deliver it elsewhere when the workflow requires.
npm install @remac/sdk
billing-context.ts
const result = await client.askContext("customer-billing", {
question:
"Can this customer receive a refund for the duplicate annual charge?",
input: { customer_id: "cus_8142" },
saveAnswer: false,
});
console.log(result.answer);Use Remac inside the tools you already run.
MCP connects supported agents and coding tools. Applications using OpenRouter can call a configured context through an SDK or HTTP and use the returned answer in their workflow.
Coding agents and IDEs
Claude Code
Cursor
GitHub Copilot
OpenAI CodexAgent systems and model routing
OpenClaw
Hermes Agent
OpenRouterChoose how your code calls Remac.
Every method uses the same request meaning. Switch languages or use the HTTP and MCP contracts directly.
billing-context.ts
const result = await client.askContext("customer-billing", {
question:
"Can this customer receive a refund for the duplicate annual charge?",
input: { customer_id: "cus_8142" },
saveAnswer: false,
});
console.log(result.answer);Start with the job you need to finish.
Each guide connects a Remac access method to a complete developer workflow.
Context / TypeScript SDK
Answer a billing question during a support request
Call a configured billing context and return a grounded answer with its supporting records.
Open guideAgents / MCPConnect Remac to a coding agent through MCP
Call a configured Remac context from Claude Code, Cursor, GitHub Copilot, or Codex.
Open guideContext / Python SDKAsk context kept ready before the request
Ask a configured synchronized context and return an answer grounded in its current records.
Open guidePipelines / Go SDKKeep product policies synchronized in Qdrant
Prepare selected Notion content, create embeddings where required, and replace the matching vector points.
Open guidePipelines / HTTP APIDeliver one payment event to three systems
Send separate prepared outputs to Kafka, Amazon S3, and an HTTPS case endpoint from one Pipeline run.
Open guideOperations / HTTP APIInspect every destination result
Read the Pipeline execution and see which configured destinations are pending, delivered, or failed.
Open guideLess source work inside every new workflow.
Remac keeps source access, context preparation, and destination delivery behind stable contracts.
Read once per Pipeline run
Remac prepares a separate payload for each selected destination after the source returns.
Retry without another source read
A safe destination retry reuses the stored payload. It does not repeat preparation.
Separate result for each destination
One failed destination does not erase a confirmed result from another destination.
Put current source data inside the next agent or application you build.
Start with one context request, then add synchronized context or destination delivery when the workflow needs it.