Calculate Tiered Fee
finance.tiered_fee
Overview
Apply a progressive or cliff tier schedule to one non-negative decimal base with deterministic ordered segment receipts and no hidden rounding or inferred boundaries.
We provide reproducible fee segmentation rather than prompt arithmetic.
Reliability
FEE_INPUT_INVALID and ITEM_LIMIT_EXCEEDED identify exact repair classes.
Context footprint
One call returns the total and compact segment proof. A successful call costs 1 execution credit.
When to use it
Use this when you have one complete explicit tier schedule.
Avoid this when schedule terms are missing.
Scope
Non-goals
- Does not infer or persist fee schedules.
- Does not round currency amounts.
Properties
Capabilities
Cost & billing
Flat rate per invocation
File handling
How we handle your data
What this means
This skill may receive sensitive content, but it does not target sensitive data and returns only a structured non-sensitive result.
Squillify guarantees
- Runs inside Squillify
- This skill runs inside Squillify.
- Payloads are not sent to an external service by this skill.
- Squillify does not permanently store submitted payloads.
- Telemetry records metadata only, not submitted content.
- Submitted payloads are not used for training.
- Submitted payloads are not reviewed by humans.
- This skill does not target sensitive data.
- The response does not contain submitted content.
Your responsibility
Squillify does not determine whether submitted content is sensitive. Your application is responsible for deciding what data it is allowed to submit. Your application is responsible for securing the response.
Input schema
| Field | Type | Required | Description |
|---|---|---|---|
| base | string | Yes | Non-negative plain decimal base the schedule is applied to. |
| tiers | array | Yes | Ordered 1 through 100 closed tier objects {upTo?,rate}; only the final upTo may be omitted. |
| tierMode | string | Yes | Whether each band is charged progressively or the whole base uses the selected cliff tier. |
Output schema
| Field | Type | Required | Description |
|---|---|---|---|
| feeAmount | string | Yes | Normalized plain-decimal sum of every ordered segment fee without implicit rounding. |
| segments | array | Yes | Ordered array of closed segment objects {from,to?,rate,appliedBase,fee}; to is omitted only for the open final tier. |
| tierMode | string | Yes | Selected tier mode repeated in the receipt so fee segmentation remains independently auditable. |
API contract
POST /v1/executecurl -sS -X POST "$BASE/v1/execute" -H "Authorization: Bearer $KEY" -H 'Content-Type: application/json' -d '{"skillKey":"finance.tiered_fee","input":{"base":"150","tiers":[{"upTo":"100","rate":"0.01"},{"rate":"0.02"}],"tierMode":"PROGRESSIVE"}}'import { Squillify } from "@squillify/sdk";
const sq = new Squillify({ apiKey: process.env.SQUILLIFY_API_KEY });
const { output } = await sq.execute("finance.tiered_fee", {"base":"150","tierMode":"PROGRESSIVE","tiers":[{"upTo":"100","rate":"0.01"},{"rate":"0.02"}]});Errors
| Code | HTTP | Retryable | Description |
|---|---|---|---|
| VALIDATION_ERROR | 400 | No | The request payload failed schema validation. |
| UNAUTHORIZED | 401 | No | Missing or invalid API key. |
| SKILL_NOT_ACCESSIBLE | 403 | No | The API key is not granted access to this skill. |
| SKILL_NOT_AVAILABLE_FOR_PLAN | 403 | No | This skill is not included in your current plan. |
| PLAN_ELIGIBILITY_UNAVAILABLE | 503 | Yes | Plan eligibility could not be decided. Retry after backoff. |
| SKILL_NOT_FOUND | 404 | No | The requested skill or version does not exist. |
| TENANT_RATE_LIMITED | 429 | Yes | Request rate limit exceeded. Retry after backoff. |
| QUOTA_EXCEEDED | 429 | Yes | Plan quota exhausted. Retryable once the quota period resets. |
| EXECUTION_TIMEOUT | 504 | Yes | Execution exceeded the allowed time budget. |
| FEE_INPUT_INVALID | 400 | No | The request payload failed this skill's input validation. |
| ITEM_LIMIT_EXCEEDED | 429 | No | A size, quota, rate, or time limit was exceeded. |
Other limits
| Limit | Value |
|---|---|
| Recommended inline bytes | 32 KiB |
Limitations
- Does not infer or persist fee schedules.
- Does not round currency amounts.
- Unbounded or implicit schedules.
How to call
POST /v1/execute (requires authentication)
{
"skillKey": "finance.tiered_fee",
"input": {
"base": "150",
"tierMode": "PROGRESSIVE",
"tiers": [
{
"upTo": "100",
"rate": "0.01"
},
{
"rate": "0.02"
}
]
}
}Examples
Progressive management fee
{
"base": "150",
"tierMode": "PROGRESSIVE",
"tiers": [
{
"upTo": "100",
"rate": "0.01"
},
{
"rate": "0.02"
}
]
}{
"tierMode": "PROGRESSIVE",
"feeAmount": "2",
"segments": [
{
"from": "0",
"to": "100",
"rate": "0.01",
"appliedBase": "100",
"fee": "1"
},
{
"from": "100",
"rate": "0.02",
"appliedBase": "50",
"fee": "1"
}
]
}Cliff management fee
{
"base": "150",
"tierMode": "CLIFF",
"tiers": [
{
"upTo": "100",
"rate": "0.01"
},
{
"rate": "0.02"
}
]
}{
"tierMode": "CLIFF",
"feeAmount": "3",
"segments": [
{
"from": "0",
"to": "100",
"rate": "0.01",
"appliedBase": "0",
"fee": "0"
},
{
"from": "100",
"rate": "0.02",
"appliedBase": "150",
"fee": "3"
}
]
}Recommended use cases
- Management-fee schedule evaluation.
- Independent tier receipt verification.
Avoid for
- Unbounded or implicit schedules.
Related skills
Composable with
Safety & privacy
- Runs without calling any external service.
- Your payloads are never stored permanently.
- Telemetry captures metadata only — never your payload contents.
- We never train models on your payloads.
- No human reviews your payloads.