Description
Preserve explicit foreign-agent territory and exclusivity assertions.
Cross-border business records combine named parties, contract versions, currencies, fees, shipment terms and local-time transcriptions. A supplied rate direction or fee currency determines arithmetic, while an authentic-language or trade-rule label remains a record assertion. Local calculations do not establish actual settlement or governing obligations.
Preserve explicit foreign-agent territory and exclusivity assertions.
When to use this tool
Use Foreign Agent Territory Exclusivity Token when you already have agreementId, agentId, territoryText, suppliedExclusivity and need to preserve explicit foreign-agent territory and exclusivity assertions.
How to use the tool and how it works
- Enter agreementId, agentId, territoryText, suppliedExclusivity. Use the units and conventions below.
- Run the tool. Correct any format, range, or cross-field input error before interpreting the output.
- Read token. Use the output convention below.
Enter agreementId, agentId, territoryText, suppliedExclusivity using the field constraints below. Encode these values, in exactly that order, as a JSON array and return the serialized array as text in token. String values are preserved without trimming or external terminology lookup.1
| Input field | Meaning and units | Accepted input |
|---|---|---|
| agreementId | Agreement Id | Required. Text; minimum UTF-16 length 1; maximum UTF-16 length 8192. |
| agentId | Agent Id | Required. Text; minimum UTF-16 length 1; maximum UTF-16 length 8192. |
| territoryText | Territory Text | Required. Text; minimum UTF-16 length 1; maximum UTF-16 length 8192. |
| suppliedExclusivity | Supplied Exclusivity | Required. Text; minimum UTF-16 length 1; maximum UTF-16 length 8192. |
| Output field | Interpretation | Returned shape |
|---|---|---|
| token | Token | Required. Text; maximum UTF-16 length 8192. |
{
"input": {
"agreementId": "A17",
"agentId": "G4",
"territoryText": "Region A",
"suppliedExclusivity": "exclusive"
},
"output": {
"token": "[\"A17\",\"G4\",\"Region A\",\"exclusive\"]"
}
}Limitations and assumptions
- The result records supplied values without interpreting or enforcing agreements. Sources and asserted relationships are not independently authenticated.
- Inputs must satisfy both the field types and the cross-field conditions above. Invalid input causes an error; a successful false flag or documented placeholder is a different result.
Alternative or Complementary methods
Review the original agreement, invoice, shipment and payment records with their stated editions and currency bases. Use complete contractual and valuation rules for actual obligations; supplied shares, labels and conversions are auditable components of that review.
References
Similar or alternative tools
- Shipment Document Reference Token
Associate an explicitly identified shipment document with its shipment.
- Documentary Credit Expiry Place Timezone
Preserve explicit documentary-credit expiry time, place and clock metadata.