Same response structure
SDK, HTTP, and MCP return the same context fields and source identity.
Build with current source data.
Give any agent or application the data this step needs through an SDK, HTTP, or MCP. Keep it ready or deliver it elsewhere when the workflow requires.
npm install @remac/sdk
billing-context.ts
import {
ContextModeImmediate,
OperationSaved,
RemacClient,
} from "@remac/sdk";
const client = new RemacClient({
apiKey: process.env.REMAC_API_KEY,
});
const context = await client.retrieveContext({
mode: ContextModeImmediate,
question:
"Retrieve this customer's active subscription, invoices from the last 90 days, payment authorizations, open billing cases, and current refund rules.",
targets: [{
source_id: "src_3IwUXvAFxyH1oNYNbokDbW4czWf",
operation: OperationSaved,
input: {
operation_id: "op_3IwUXtXUm0HdpgglZBML693GZRt",
input: { customer_id: "cus_8142" },
},
}],
result_limit: 20,
save_result: false,
});Use Remac inside the tools you already run.
MCP connects supported agents and coding tools. Applications using OpenRouter call Remac through an SDK or HTTP before the model request.
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
import {
ContextModeImmediate,
OperationSaved,
RemacClient,
} from "@remac/sdk";
const client = new RemacClient({
apiKey: process.env.REMAC_API_KEY,
});
const context = await client.retrieveContext({
mode: ContextModeImmediate,
question:
"Retrieve this customer's active subscription, invoices from the last 90 days, payment authorizations, open billing cases, and current refund rules.",
targets: [{
source_id: "src_3IwUXvAFxyH1oNYNbokDbW4czWf",
operation: OperationSaved,
input: {
operation_id: "op_3IwUXtXUm0HdpgglZBML693GZRt",
input: { customer_id: "cus_8142" },
},
}],
result_limit: 20,
save_result: false,
});Start with the job you need to finish.
Each guide connects a Remac access method to a complete developer workflow.
Context / TypeScript SDK
Retrieve current billing facts during a support request
Call one saved source operation and return the current subscription, payment, case, and policy records.
Open guide →Agents / MCPConnect Remac to a coding agent through MCP
Add the Remac MCP endpoint, then call retrieve_context from Claude Code, Cursor, GitHub Copilot, or Codex.
Open guide →Context / Python SDKSearch context kept ready before the request
Create a Collection, keep it current with a Pipeline, then retrieve records in synchronized mode.
Open guide →Pipelines / Go SDKKeep product policies synchronized in Qdrant
Prepare selected Notion content, create embeddings where required, and replace the matching vector points.
Open guide →Pipelines / 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 guide →Operations / HTTP APIInspect every destination result
Read the Pipeline execution and see which configured destinations are pending, delivered, or failed.
Open guide →Less 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.