Calculate count days
time.count_days
Overview
Perform deterministic bounded count days from explicit ISO dates and an immutable caller-supplied calendar, returning deterministic receipt fields without wall-clock, locale, network, or inferred-holiday state.
We provide a bounded calendar result so you receive explicit version receipts.
Reliability
CALENDAR_INPUT_INVALID means dates, calendar, convention, or bounds are invalid; correct the closed request before retrying.
Context footprint
One call replaces prompt date loops. A successful call costs 1 execution credit.
When to use it
When you hold two ISO dates and an explicit includeStart/includeEnd pair and need the counted calendar-day span.
Avoid when the span must skip weekends or holidays — use time.business_days_between.
Scope
Non-goals
- Does not fetch calendars or infer conventions.
- Does not read the wall clock.
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 |
|---|---|---|---|
| startDate | string | Yes | Inclusive or exclusive start date. |
| endDate | string | Yes | Inclusive or exclusive end date. |
| includeStart | boolean | Yes | Whether startDate is counted. |
| includeEnd | boolean | Yes | Whether endDate is counted. |
Output schema
| Field | Type | Required | Description |
|---|---|---|---|
| dayCount | integer | Yes | Counted calendar days. |
| includeStart | boolean | Yes | Applied start-boundary choice. |
| includeEnd | boolean | Yes | Applied end-boundary choice. |
API contract
POST /v1/executecurl -sS -X POST "$BASE/v1/execute" -H "Authorization: Bearer $KEY" -H 'Content-Type: application/json' -d '{"skillKey":"time.count_days","input":{"startDate":"2026-01-01","endDate":"2026-01-03","includeStart":true,"includeEnd":false}}'import { Squillify } from "@squillify/sdk";
const sq = new Squillify({ apiKey: process.env.SQUILLIFY_API_KEY });
const { output } = await sq.execute("time.count_days", {"startDate":"2026-01-01","endDate":"2026-01-03","includeStart":true,"includeEnd":false});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. |
| CALENDAR_INPUT_INVALID | 400 | No | The request payload failed this skill's input validation. |
Other limits
| Limit | Value |
|---|---|
| Recommended inline bytes | 32 KiB |
Limitations
- Does not fetch calendars or infer conventions.
- Does not read the wall clock.
- Unversioned external holiday sources.
How to call
POST /v1/execute (requires authentication)
{
"skillKey": "time.count_days",
"input": {
"startDate": "2026-01-01",
"endDate": "2026-01-03",
"includeStart": true,
"includeEnd": false
}
}Examples
Verified calendar vector
{
"startDate": "2026-01-01",
"endDate": "2026-01-03",
"includeStart": true,
"includeEnd": false
}{
"includeEnd": false,
"dayCount": 2,
"includeStart": true
}Repeated calendar vector
{
"startDate": "2026-01-01",
"endDate": "2026-01-03",
"includeStart": true,
"includeEnd": false
}{
"includeEnd": false,
"dayCount": 2,
"includeStart": true
}Recommended use cases
- Explicit deterministic calendar calculation.
- Independent business-date and calendar receipt verification.
Avoid for
- Unversioned external holiday sources.
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.