Calculate a Safe Ratio
math.safe_ratio
Overview
Divide two decimals with explicit zero-denominator behavior. Inputs are bounded plain decimals, output order follows input order, and no currency, policy, materiality threshold, market data, or ambient default is inferred.
For Calculate a Safe Ratio, we publish the exact bounded decimal rule and audit fields so you do not have to trust approximate prompt arithmetic.
Reliability
Calculate a Safe Ratio is STRICT and stateless: the same bounded input produces the same normalized output. DECIMAL_INVALID means a value is malformed or outside the 100-digit/scale-40 ceilings; fix it before retrying. ITEM_LIMIT_EXCEEDED means an array exceeds 10,000 entries; split it. ZERO_DENOMINATOR means a denominator or weight sum is zero; change it or select the documented zero policy. ROUNDING_INVALID means mode, scale, or quantization is invalid; send a supported mode and scale. ALLOCATION_INVALID means weights, ids, or total violate the published allocation rules; correct the named structure.
Context footprint
For Calculate a Safe Ratio, one bounded call replaces an error-prone arithmetic prompt and returns normalized decimal strings. A successful call costs 1 execution credit.
When to use it
When a numerator and denominator must be divided with an explicit zero-denominator policy.
When you need percent change from a baseline, or the zero policy is still unspecified.
Scope
Non-goals
- Does not infer a rounding, materiality, currency, or business policy
- Does not fetch market data or invoke another public skill
- Does not accept unbounded arrays or binary floating-point semantics
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 |
|---|---|---|---|
| numerator | string | Yes | Required plain-decimal numerator. |
| denominator | string | Yes | Required plain-decimal denominator; zero follows zeroPolicy. |
| zeroPolicy | string | No | Optional error, undefined or zero; omitted means error. |
Output schema
| Field | Type | Required | Description |
|---|---|---|---|
| defined | boolean | Yes | True when denominator was non-zero. |
| ratio | string | No | The ratio; omitted only for zeroPolicy undefined. |
API contract
POST /v1/executecurl -sS -X POST "$BASE/v1/execute" -H "Authorization: Bearer $KEY" -H 'Content-Type: application/json' -d '{"skillKey":"math.safe_ratio","input":{"numerator":"3","denominator":"4"}}'import { Squillify } from "@squillify/sdk";
const sq = new Squillify({ apiKey: process.env.SQUILLIFY_API_KEY });
const { output } = await sq.execute("math.safe_ratio", {"denominator":"4","numerator":"3"});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. |
| DECIMAL_INVALID | 400 | No | The request payload failed this skill's input validation. |
| ZERO_DENOMINATOR | 400 | No | The request payload failed this skill's input validation. |
Other limits
| Limit | Value |
|---|---|
| Recommended inline bytes | 32 KiB |
Limitations
- Does not infer a rounding, materiality, currency, or business policy
- Does not fetch market data or invoke another public skill
- Does not accept unbounded arrays or binary floating-point semantics
- When you need percent change from a baseline, or the zero policy is still unspecified.
- Do not use for approximate floating-point analytics or unbounded datasets
How to call
POST /v1/execute (requires authentication)
{
"skillKey": "math.safe_ratio",
"input": {
"denominator": "4",
"numerator": "3"
}
}Examples
Three divided by four
{
"denominator": "4",
"numerator": "3"
}{
"ratio": "0.75",
"defined": true
}Explicitly map a zero denominator to zero
{
"numerator": "8",
"denominator": "0",
"zeroPolicy": "zero"
}{
"ratio": "0",
"defined": false
}Recommended use cases
- When a numerator and denominator must be divided with an explicit zero-denominator policy.
- Use in auditable fund-accounting calculations that need normalized decimal output
Avoid for
- When you need percent change from a baseline, or the zero policy is still unspecified.
- Do not use for approximate floating-point analytics or unbounded datasets
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.