Needlepath · Context selection for AI agents

Smarter, faster agents. Needlepath sends your model only what matters.

Agents slow down and make mistakes when every step carries everything. Needlepath keeps the evidence the step needs, in your own words, before every model call.

Better answers
+12.9 pp
than sending the full document
Faster calls
504 ms
faster at p95, end to end, on the same 2,600 answers
Decided in
25.0 ms
on average, no GPU
Fewer tokens
52.9%
fewer input tokens sent, counting the 24.0% of calls that got the whole document

Keep your model. Change one call. Pay as you go.

RECORDED CALL · REAL RESPONSE 1 / 5
QuestionCan invoice INV-4471 for account acct-2213 still be refunded, and for how much?
get_invoice(INV-4471)Damaged on arrival policy v3Refund policy v4get_invoice(INV-4468)Shipping and delivery policy v2Warranty terms v2Data retention policy v7get_shipment(SHP-77120)get_shipment(SHP-77081)Gift card terms v1get_account(acct-2213)Changing a delivery addressCustomer, message 1Agent, message 1Customer, message 2Tax exemption certificatesgateway timeout on refund previewBulk order discountsrefund_preview(INV-4471), attempt 2issue_refundDownloading an invoice PDFget_account(acct-1180)Loyalty pointsWarehouse notice, July 15get_catalog_item(HV-CHAIR-04)Price match policy v1get_carrier_alerts(Corvane Freight)Cancelling an order before it shipsget_open_tickets(acct-2213)Returns for unwanted items v5Business workspace plansSSO and SCIM provisioning guide, revision 12
3of 32 records sent in
2,928 to 160tokens
5.9 msto decide
Kept the 3 records that answer the question. Left 29 out.
Records are from the request; selections, tokens and timing from the response. Titles shortened to fit. Open the full replay
Backed & built with NVIDIA Inception Google for Startups AWS Activate Babson Butler Launchpad ND Labs
The Problem

Every step reads everything, and pays for it.

Each tool call, document, memory read and workflow step adds to the context. The next model call reads all of it: more tokens, more time, and more chances to act on the wrong detail. The usual fixes each cost something too.

SEND EVERYTHING

Attention gets diluted

Every extra page costs input tokens and competes for the model's attention, whether or not it helps this step.

REWRITE IT SHORTER

Details go missing

A summary fits nicely, and can leave out the exact name, amount or order detail the next step needs, without saying so.

BUILD RETRIEVAL

You own a system

Chunking, tuning and evals that drift every time the corpus changes, on someone's on-call rotation.

Needlepath sends your own records, unrewritten, and only the ones the step needs.

When the whole file is what the moment needs, it hands over the whole file. It decides in milliseconds, with no second model in the loop, and every response lists what was sent and what was left out.

Measured

Better answers at half the tokens, on a public benchmark.

Scored on the NVIDIA RULER benchmark, 2,600 questions, one run, official scorer, against sending everything.

  1. 1Answers were +12.9 pp better than sending the full document.
  2. 2Answering was 504 ms faster at p95 with Needlepath in the stack, end to end. The decision itself took 25.0 ms on average.
  3. 352.9% fewer input tokens were sent, counting the 24.0% of calls that received the complete document.
  4. 4The bill was 44.31% lower all in: $38.44 with Needlepath vs $69.02 sending everything, our fee included.
  5. 5Other preparation methods, measured on the same items, took 1.13 to 32.4 s per item in selection latency alone, some needing a GPU.
On your bill
Off the model bill each month$19,044before Needlepath's fee
2.1xthe calls on the same input-token capacitytheoretical, prefill-bound; measured on your traffic in a workload review

Estimate your savings here, or request a workload review and we measure the real share on your traffic. Starting point: the cost calculator's example month and the public test's 52.9%, counting the 24.0% of calls that received the complete document.

How It Works

One call before every model call.

01

Send what you hold

Documents, tool results, chat history, memory, workflow state. Send the records as they are, with the question the model is about to answer.

02

Needlepath picks

Needlepath returns the records most relevant to the question, in milliseconds.

03

The model gets what matters

Your originals, unrewritten. When the whole set is what the question needs, the whole set goes through unchanged.

Needlepath decides what enters the model call, across documents, tool results, memory and workflow state, and keeps every record in your words. Each response lists the records it sent and the ones it left out, so every step has a record of what the model saw. Read the API docs.
Start In Three Steps

Copy, paste, run.

One key, one call before your model call, and a dashboard to watch it. The code below is the same as the docs; swap in your records and your prompt.

  1. 1
    Sign up and get an API key

    Sign up for public beta today. The key is minted in the console and lives in your environment as NEEDLEPATH_API_KEY.

  2. 2
    Send your records and your prompt, get the context back, call your model
    pip install needlepath
    import os
    from needlepath import NeedlepathClient, ContextRecord, TaskSpec
    from openai import OpenAI
    
    client = NeedlepathClient(api_key=os.environ["NEEDLEPATH_API_KEY"], operating_point="np-2026-08-r4")
    
    # One record per item the agent holds: purchase orders, the supplier contract, the conversation so far.
    records = [ContextRecord(text=po.text, kind="external_data", id=po.id, title=po.title) for po in purchase_orders]
    prompt = "Which Corvane Freight purchase orders are still open past their delivery date?"
    
    result = client.select(records=records, task=TaskSpec(prompt=prompt), max_context_tokens=4000)
    context = result.rendered_context if result.applied else "\n\n".join(r.text for r in records)
    
    # Your model call, unchanged, with the context ahead of the prompt.
    answer = OpenAI().chat.completions.create(
        model="your-model", messages=[{"role": "user", "content": f"{context}\n\n{prompt}"}]
    )
  3. 3
    Watch it work

    Requests, tokens metered and tokens saved, per key, in the console. When Needlepath stands aside, the whole set goes through unchanged.

Full clients, the LlamaIndex integration and the rules every integration follows: docs.nextmoca.com/integrations.

Two Ways To Deploy

In our cloud, or inside yours.

Start hosted in an afternoon, or keep everything inside your network. Same engine, same results, your call.

HOSTED

Drop in. One API key.

Install the client, point it at your workload, and Needlepath prepares the context before every model call.

  • TypeScript and Python clients
  • Context selection in milliseconds
  • Shadow mode first: zero-risk evaluation
Sign up for public beta today

Or review your workload first.

IN YOUR NETWORK

Runs where your data lives.

Deployed into your VPC or data center, next to your models, and tuned for your workloads.

  • Everything in hosted, plus
  • Your records never leave your network, so data residency, retention and regulatory requirements are met where they already are
  • Higher throughput with lower latency
  • Dedicated support
Talk to us

Prefer to talk first? Book a 30-minute call

Integrations

Integrates seamlessly with your existing tech stack.

Each integration runs one step before the call you already make, so nothing in your agent code changes to use it. When Needlepath stands aside, it returns your original context unchanged, and your call proceeds exactly as before, the same way on every integration.

Not on the list? Needlepath is three REST endpoints. Explore the API

By Task

The same public exam, task by task.

Each measured against sending everything.

WINFinding one buried fact+17 points at 8K, +21 at 16KStatistically significant at both sizes.
WINMany needles, one answer+16 points at 8K, +20 at 16KA consistent gain.
WINCounting and extraction+15 points at 8K, +23 at 16KTask-level gains at both context lengths.
WINHard multi-key lookups+13 points at 8K, +12 at 16KStatistically significant.
EVENLong-document QApooled -2.0 points, interval includes zeroStatistically even with sending everything. Needlepath keeps more, or steps aside, where coverage matters.
Team

Hyperscale operators and engineers who built and shipped agentic infrastructure at billion-dollar revenue scale. We are building Next Moca because we know what the next ten years of enterprise AI actually need.

Kiran Kashalkar
Kiran Kashalkar
Co-CEO & Co-Founder

Repeat builder. Co-founded and served as CTO of Green Piñata Toys (acquired). Director of Engineering at Oracle (OCI) and Brightcove, with prior leadership roles at Juniper, Cisco, and others. Built and scaled world-scale services for customers like ByteDance and HBO. Architect behind Next Moca's agentic orchestration and infrastructure layers. MBA (Babson), M.S. Computer Science (Penn State), B.E. Computer Engineering (University of Mumbai).

ex-CTO Green Piñataex-Director Oracle · BrightcoveCisco · JuniperBabson MBA · Penn State MS
Swanand Rao
Swanand Rao
Co-CEO & Co-Founder

Product-driven inventor with a track record of bootstrapping new products, blending deep engineering with go-to-market focus. Director of Product at Adobe, with prior leadership roles at Microsoft, Oracle, and others. Holds multiple patents in distributed systems. Architect behind Next Moca's agentic foundations and core AI services. Executive MBA (Michigan Ross), M.S. Computer Science (USC), B.E. Computer Engineering (University of Mumbai).

ex-Director AdobeMicrosoft · OracleDistributed-systems patentsRoss EMBA · USC MS
Paru Somashekar
Paru Somashekar
Founding Member of Technical Staff · Agent Experiences

Engineering and UX leader with 25+ years at Sun Microsystems and Oracle. Founding Member of Technical Staff at Next Moca, leading Agent Experiences. Expertise in UI/UX architecture, data security, and full-stack engineering.

Founding MTSSun · OracleUI/UX architectureFull-stack engineering
Backed by

Operators who built and shipped enterprise platforms at billion-dollar scale. They're betting on Next Moca because they've lived the problem we're solving.

Namita Dhallan
Namita Dhallan
Lead investor · Managing Partner, ND Labs

Ran product and strategy at Brightcove (CPO) and Ellucian (CPO) over two decades of enterprise SaaS leadership. Now Managing Partner at ND Labs and lead investor in Next Moca.

ND Labsex-CPO Brightcoveex-CPO EllucianEnterprise SaaS
Rohit Puri
Rohit Puri, Ph.D.
Advisor · VP of Engineering ML Platform, Capital One

Head of ML Platform at Capital One, operating production AI infrastructure for one of the largest regulated U.S. banks. Ph.D. in EECS from UC Berkeley, M.S. from UIUC, and B.Tech. from IIT Bombay.

Capital One ML HeadUC Berkeley Ph.D.Regulated enterprises
Questions

Five answers before you decide.

What does Needlepath do?

Needlepath decides what enters each model call. Send the records your agent holds with the question the model is about to answer, and it returns the ones the step needs, unrewritten, in milliseconds. When the whole set is what the question needs, the whole set goes through unchanged.

How much does Needlepath save?

On the NVIDIA RULER benchmark, 2,600 questions, the bill was 44.31% lower all in with our fee included, with 52.9% fewer input tokens sent, counting the 24.0% of calls that received the complete document. Answers were +12.9 pp better than sending everything.

Does it rewrite or summarize my documents?

No. Needlepath sends your own records, unrewritten, and only the ones that answer the question. It does not summarize, compress or rerank the content of a record.

What happens when the whole file is what the question needs?

It hands over the whole file. When a smaller context cannot be shown to be safe, the complete document goes through unchanged, so what you risk on that call is paying full price.

How do I start?

Sign up for the public beta, create an API key, and add one call before each model call with the Python or TypeScript client. Keep your model. Pay as you go. Or request a workload review and we compare answer quality, token use, latency and cost on your own traffic.

Your Workload

Try Needlepath on your own workload.

Keep your model. Change the endpoint. Compare answer quality, token use, latency and cost on your traffic. Tell us what you are building and we reply within one business day. No commitment.

We handle your information as described in our Privacy Policy.

Prefer to talk first? Book a 30-minute call. Already decided? Sign up for public beta today.

kiran@nextmoca.com · swanand@nextmoca.com · Boston, MA · Palo Alto, CA

Every figure on this page is from one run of Needlepath at operating point np-2026-08-r4 on RULER, 2,600 questions, official scorer. Full results.