feat: add Kiprio.com APIs (email-validate, bizday, hash)

[ForeverTools]

New APIs: kiprio.com

Adding 3 APIs from Kiprio.com — a developer-focused API platform providing utility HTTP endpoints.

APIs added:

1. Email Validation (/v1/email-validate)

   • Syntax validation, MX record check, disposable/role-based/free-provider detection
   • Spec: https://kiprio.com/v1/email-validate/openapi.json

2. Business Days Calculator (/v1/bizday)

   • Business day counting between dates, supports 100+ countries/regions, public holidays
   • Spec: https://kiprio.com/v1/bizday/openapi.json

3. Hash & Encode (/v1/hash)

   • MD5, SHA-1/256/384/512, SHA3-256/512 hashing, HMAC signing, Base64/hex encoding
   • Spec: https://kiprio.com/v1/hash/openapi.json

All specs are OpenAPI 3.0.3, served from stable URLs on kiprio.com (cPanel, 99.9% uptime).
Free demo tier on every endpoint, no key required for testing.

[gemini-code-assist]

Code Review

This pull request introduces three new OpenAPI 3.0.3 specifications for Kiprio's Business Days Calculator, Email Validation, and Hash & Encode APIs. The review feedback focuses on enhancing the robustness of these definitions for better client generation. Key recommendations include adding missing response content for the HMAC endpoint, defining required properties across all response schemas to ensure consistent model generation, and maintaining consistency for date formats and algorithm enums across different operations.

[gemini-code-assist]

The 200 response for the /hmac endpoint is missing a content definition. Without a schema, client generators cannot produce typed responses for this operation.

          description: HMAC result
          content:
            application/json:
              schema:
                type: object
                required:
                  - input
                  - algo
                  - hash
                properties:
                  input:
                    type: string
                  algo:
                    type: string
                  hash:
                    type: string

[gemini-code-assist]

The response schema should define required properties to ensure consistent behavior in generated clients. Additionally, the from and to fields in the response should include format: date to match the input parameters.

                type: object
                required:
                  - from
                  - to
                  - business_days
                  - calendar_days
                  - country
                properties:
                  from:
                    type: string
                    format: date
                  to:
                    type: string
                    format: date

[gemini-code-assist]

It is best practice to specify which properties are required in the response schema. This helps client generators create more accurate models.

                type: object
                required:
                  - input
                  - valid
                  - syntax_ok
                  - mx_found
                  - disposable
                  - role_based
                  - free_provider
                  - confidence
                properties:

[gemini-code-assist]

The response schema for the hash operation should define required properties to ensure the output is correctly parsed by generated clients.

                type: object
                required:
                  - input
                  - algo
                  - hash
                properties:

[gemini-code-assist]

The algo property in the HMAC request body should include the same enum as the GET endpoint to restrict inputs to supported algorithms and improve documentation.

                algo:
                  type: string
                  enum: [md5, sha1, sha256, sha384, sha512, sha3-256, sha3-512]
                  default: sha256