LLPROBeta

Home / Businesses / Territory Assignment by ZIP Prefix

Territory Assignment by ZIP Prefix

Assign sales accounts to territories from your ZIP prefix table: longest prefix wins, unassigned accounts and prefixes claimed twice listed, a count per territory, and a signed record.

Testing

What it does
Assign sales accounts to territories from your ZIP prefix table: longest prefix wins, unassigned accounts and prefixes claimed twice listed, a count per territory, and a signed record.
Who it is for
Businesses.
Start in one step
Ask your agent to call territory_assign_zip at llpro.ai/mcp (free, no sign-up). This page explains the tool; it has no form to run it.
What to expect
Testing: open to try. Free

New to this? Start here.

What it does

Territory Assignment by ZIP Prefix is for agents that plan or maintain sales territories for a business and must route every account to one owner the same way every time, with gaps and overlaps called out. Assign sales accounts to territories from a ZIP Code prefix table you send. Send the territories, each with its ZIP prefixes (1 to 5 digits: 7 for a whole national area, 770 for a 3-digit area, 77002 for one ZIP Code), and the accounts with their US ZIP Codes. Each account goes to the territory with the longest prefix that matches its ZIP. Get back every account's territory and matched prefix, the accounts left unassigned, prefixes claimed by two territories (conflicts: those accounts are not assigned), nested prefixes across territories, and the count per territory. It is one of the Sales (CRM) department tools LLPRO builds for the work agents do across business software (Salesforce, HubSpot, Pipedrive, Zoho Crm, Dynamics 365). Every answer carries the written rule it used, what it does not do, its sources with dates, and an Ed25519 signature you can check against the key below.

Who it is for
Agents that plan or maintain sales territories for a business and must route every account to one owner the same way every time, with gaps and overlaps called out.
Price
Free, no sign-up: 120 calls an hour per address and 3,000 an hour across all callers. Paid calls are planned and not charging.
Limits
Up to 30,000 bytes per call, territories up to 100 entries, accounts up to 200 entries; larger requests are refused, never cut. Unknown fields are refused with the list of accepted ones. Nothing you send is stored by the tool; no model and no network are used. Does not look up ZIP Codes (nothing is fetched): it does not check that a ZIP Code exists, which city or county it is in, or which ZIP Codes a USPS 3-digit area holds, and it has no built-in territory map: the prefix table you send is the plan. Does not handle Canadian or other postal codes, split a ZIP Code that crosses a territory line, balance workload, or decide who owns a conflict. Not legal advice.

For developers: try it

POST https://llpro.ai/mcp
{"jsonrpc": "2.0", "id": 1, "method": "tools/call", "params": {"name": "territory_assign_zip", "arguments": {"territories": [{"territory": "HOU", "prefixes": ["770", "773"]}, {"territory": "DFW", "prefixes": ["750", "752"]}, {"territory": "CENTRAL-TX", "prefixes": ["7", "77002"]}], "accounts": [{"account": "ACC-1", "zip": "77002-1234"}, {"account": "ACC-2", "zip": "77345"}, {"account": "ACC-3", "zip": "75201"}, {"account": "ACC-4", "zip": "78701"}, {"account": "ACC-5", "zip": "10001"}]}}}

For agents

Tool territory_assign_zip on https://llpro.ai/mcp and in the tools list. Signed answers are checked with the public key below (signer llpro1:jrrhzb5l6hnfqydz43yzsm5efy): an Ed25519 signature over the observation as canonical JSON (sorted keys, no spaces).

Public key (base64): uwRy/KzjQk2M8JEy2e/bUhK2+et9btTRDBBV+dt6uDY=

For agents that search MCP registries for sales territory, ZIP code prefix, territory assignment tools (listed in MCP registries, served by the LLPRO gateway: MCP, agent-to-agent and REST). One fixed, written rule per call, a signed record, no account needed.

Next

For agents: this page as Markdown · JSON · llms.txt · MCP endpoint llpro.ai/mcp · agent card