mailkube 1.0.0

checksums.yaml

@@ -0,0 +1,7 @@
+---
+SHA256:
+  metadata.gz: 7641c72078cd5550384c2e708dc156aea1f487d2304d07689ed7fcebc0868bd4
+  data.tar.gz: 4d0d9ea1e793297301d4cc7652a3ee0fa40b08dc7fcc2fa069b33cb20ddcfef2
+SHA512:
+  metadata.gz: 8abad977f64add055a7d30eb83c88529ba3602fdeeb37f7f543386f2b7683fbec70e00f28e7cd102fa1288fabf4f503dbf81cf4c616429f62539d672c3c2b499
+  data.tar.gz: dd85a8fc81e7cc52a2446bd13e70a348866694b65c0034133b4dbfe7fe8ecd31c45f82a4479216e60d783785131a5d5a27fa90ce265d86c3949493f161191cc2

data/LICENSE

@@ -0,0 +1,201 @@
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or Derivative
+          Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright 2026 Mailtactic, Corp.
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.

data/NOTICE

@@ -0,0 +1,11 @@
+mailkube-ruby
+Copyright 2026 Mailtactic, Corp.
+
+This product is licensed under the Apache License, Version 2.0 (the "License");
+you may not use this product except in compliance with the License. You may
+obtain a copy of the License at:
+
+    http://www.apache.org/licenses/LICENSE-2.0
+
+"mailkube" is a trademark of Mailtactic, Corp. Use of the name is governed by
+Section 6 (Trademarks) of the License.

data/README.md

@@ -0,0 +1,323 @@
+# mailkube-ruby
+
+[![CI](https://github.com/mailkube/mailkube-ruby/actions/workflows/ci.yml/badge.svg)](https://github.com/mailkube/mailkube-ruby/actions/workflows/ci.yml)
+[![Gem Version](https://img.shields.io/gem/v/mailkube.svg)](https://rubygems.org/gems/mailkube)
+[![License: Apache 2.0](https://img.shields.io/badge/license-Apache%202.0-blue.svg)](LICENSE)
+[![Code of Conduct](https://img.shields.io/badge/Contributor%20Covenant-2.1-purple.svg)](CODE_OF_CONDUCT.md)
+
+The official Ruby SDK for [mailkube](https://mailkube.com).
+
+Requires Ruby 3.4 or newer.
+
+## Install
+
+```bash
+bundle add mailkube
+```
+
+**Zero runtime dependencies.** The gemspec has no `add_dependency`; the standard library covers
+everything. That is deliberate — this gem is installed into other people's applications, where
+every dependency is a version conflict waiting to happen.
+
+## Usage
+
+```ruby
+require "mailkube"
+
+client = Mailkube.new # reads MAILKUBE_API_KEY
+
+email = client.emails.send(
+  from: "Acme <hello@yourdomain.com>",
+  to: "customer@example.com",
+  subject: "Hello world",
+  html: "<p>It works!</p>"
+)
+
+puts email.id
+```
+
+Create one client and reuse it.
+
+### Configuration
+
+| Option | Argument | Environment | Default |
+|---|---|---|---|
+| API key | `api_key:` | `MAILKUBE_API_KEY` | required |
+| Base URL | `base_url:` | `MAILKUBE_BASE_URL` | `https://api.mailkube.com/mta/v1/` |
+| Timeout | `timeout:` | | 30s |
+| HTTP adapter | `http:` | | `Mailkube::NetHttpAdapter` |
+
+Pass your own `http:` adapter — anything responding to
+`#call(method:, url:, headers:, body:)` and returning a `Mailkube::HttpResponse` — to route
+through a proxy, add instrumentation, or drive the client from a test.
+
+There are deliberately **no built-in retries**. A `RateLimitError` carries `retry_after` and a
+`ServerError` is safe to retry with backoff, so the calling application decides.
+
+### Idempotency
+
+Set an idempotency key on anything you might retry. The API replays the original response instead
+of sending twice.
+
+```ruby
+client.emails.send(**params, idempotency_key: "order-1234-shipped")
+```
+
+Reusing a key with a *different* payload is a `ConflictError`, not a silent overwrite.
+
+### Attachments and tags
+
+```ruby
+client.emails.send(
+  from: "Acme <hello@yourdomain.com>",
+  to: "customer@example.com",
+  subject: "Your report",
+  text: "Attached.",
+  attachments: [Mailkube::Attachment.new(filename: "report.csv", content: File.binread("report.csv"))],
+  tags: [Mailkube::Tag.new(name: "campaign", value: "welcome")]
+)
+```
+
+`content` is raw bytes; the SDK base64-encodes them for you. Tags are denormalized onto the sending
+log, so you can filter, export and dashboard by them, and they ride along on delivery webhooks.
+**Tag values are not encrypted — never put personal data in one.**
+
+## Scheduling
+
+Pass `scheduled_at:` to schedule instead of sending now. The result reports `#scheduled?`.
+
+```ruby
+email = client.emails.send(**params, scheduled_at: Time.now.utc + 3600)
+email.scheduled?    # => true
+email.status        # => "scheduled"
+```
+
+A `Time` is rendered to ISO-8601 for you; a string is passed through untouched, so it must already
+carry an offset. The instant must be in the future and within your plan's scheduling horizon.
+
+### Managing scheduled emails
+
+```ruby
+client.scheduled_emails.get(email.id)
+client.scheduled_emails.update(email.id, scheduled_at: later, batch_id: "welcome")
+client.scheduled_emails.cancel(email.id)
+```
+
+The content of a scheduled email is immutable; only its due time and batch can change.
+
+### Listing and pagination
+
+```ruby
+page = client.scheduled_emails.list(status: %w[scheduled canceled], page: 2)
+page.data              # => [Mailkube::ScheduledEmail, ...]
+page.pagination.total_count
+page.more?             # => true when the server issued a next-page link
+```
+
+Filters: `status`, `batch_id`, `scheduled_at_gte`, `scheduled_at_lte`, `page`. An omitted filter is
+never sent. Only `scheduled`, `canceled` and `failed` can be listed — a sent email has left the
+collection, so `status: "sent"` is a validation error rather than an empty result.
+
+For every page, use `iter_all`. It returns a lazy `Enumerator`, follows the server's `next` link
+rather than counting pages, and makes no request until you iterate it:
+
+```ruby
+client.scheduled_emails.iter_all(status: "scheduled").each { |email| puts email.id }
+client.scheduled_emails.iter_all.first(5)   # fetches only the pages it needs
+```
+
+`recipients` on a listed email is a **summary string** (`"a@b.com +2"`), not an array. The full
+recipient list stays server-side.
+
+### Batches
+
+Group scheduled sends under a `batch_id:` and move or cancel them as a unit:
+
+```ruby
+client.emails.send(**params, scheduled_at: due, batch_id: "welcome-2026-08")
+client.scheduled_emails.batches.update("welcome-2026-08", scheduled_at: later)
+client.scheduled_emails.batches.cancel("welcome-2026-08")
+```
+
+An unknown batch is a no-op reporting `canceled_count: 0` rather than a 404, so a count of zero is
+not a failure.
+
+## Errors
+
+Every error descends from `Mailkube::Error`, so rescue the category you care about:
+
+```ruby
+begin
+  client.emails.send(from: ..., to: ..., subject: ...)
+rescue Mailkube::RateLimitError => e
+  sleep(e.retry_after || 1)
+rescue Mailkube::APIError => e
+  warn "#{e.status_code} #{e.error_name}: #{e.message} (request #{e.request_id})"
+end
+```
+
+**Quote `request_id` when you report a failure.** Every API response carries an `X-Request-Id`, and
+a mapped `APIError` exposes it. It is the only value that lets support find your exact call in the
+server-side logs, so include it verbatim in the ticket. Setting `MAILKUBE_LOG=debug` also writes it
+on the response line, which is what makes a failure traceable from your own logs.
+
+Categories: `BadRequestError` (400), `AuthenticationError` (403), `NotFoundError` (404),
+`ConflictError` (409), `InvalidRequestError` (422), `RateLimitError` (429), `ServerError` (5xx),
+and `APIError` for anything else, which is also the parent of all of them. A transport failure
+raises `ConnectionError` and is deliberately **not** an API error.
+
+`Mailkube::ErrorName` lists the documented `name` values for discoverability. It is **not** a
+closed set: `error_name` stays a plain String, so a value this release has never heard of is
+reported verbatim rather than crashing. Scheduling adds `scheduling_not_included` (403),
+`scheduled_email_not_found` (404) and `scheduled_email_not_pending` (422).
+
+## Webhooks
+
+`Mailkube::Webhooks.verify` checks the signature and returns a typed event:
+
+```ruby
+event = Mailkube::Webhooks.verify(
+  payload: request.raw_post,      # the RAW bytes, never re-encoded JSON
+  headers: request.headers,
+  secret: ENV.fetch("MAILKUBE_WEBHOOK_SECRET")
+)
+
+case event
+when Mailkube::Events::EmailBouncedEvent
+  puts event.data.bounce.reason
+when Mailkube::Events::UnknownEvent
+  puts "newer than this SDK: #{event.type}"
+end
+```
+
+Verify against the bytes you received. Never parse the body and re-encode it first: JSON
+round-tripping reorders keys and normalizes whitespace, and the signature will not match. In Rails
+that means `request.raw_post`, not `params`. `request.headers` works directly — the SDK accepts any
+header mapping, including Rack's CGI-env spelling.
+
+`Mailkube::Webhooks.verify_signature` is the signature check alone, if you want to parse yourself.
+`X-Webhook-Id` is stable across retries; deduplicate on it.
+
+### Endpoint registration
+
+When you create an endpoint, or re-point an existing one, mailkube probes it with
+`GET <url>?hub.mode=subscribe&hub.challenge=<token>` and persists it **only** if the body echoes
+that token verbatim with a 200. Skip this and no event is ever delivered. Both webhook examples
+implement it.
+
+### Event types
+
+| Type | Envelope | Nested block |
+|---|---|---|
+| `email.sent` | `EmailSentEvent` | `data.sent` |
+| `email.delivered` | `EmailDeliveredEvent` | `data.delivery` |
+| `email.bounced` | `EmailBouncedEvent` | `data.bounce` |
+| `email.delivery_delayed` | `EmailDeliveryDelayedEvent` | `data.delay` |
+| `email.suppressed` | `EmailSuppressedEvent` | `data.suppression` |
+| `email.scheduled` | `EmailScheduledEvent` | `data.scheduled` |
+| `email.failed` | `EmailFailedEvent` | `data.failed` |
+| `email.opened` | `EmailOpenedEvent` | `data.open` |
+| `email.clicked` | `EmailClickedEvent` | `data.click` |
+| `domain.status` | `DomainStatusEvent` | `data.previous` |
+| `webhook.status` | `WebhookStatusEvent` | `data.previous` |
+
+Every `email.*` payload also carries the message context: `email_id`, `created_at`, `domain`,
+`subject`, `to`, `from` and `tags`.
+
+Two guarantees hold for every released version, so a platform change never breaks a running
+receiver:
+
+- **An unknown event type is not an error.** It parses as `Mailkube::Events::UnknownEvent`, whose
+  `data` is the raw hash.
+- **Unknown fields are preserved**, at every nesting depth. `event[...]` and `event.data[...]`
+  reach anything this release does not model, and `event.to_h` round-trips to exactly what the
+  server sent.
+
+## Logging
+
+Silent by default. Turn it on with any object responding to `#write`:
+
+```ruby
+Mailkube.enable_logging                          # $stderr
+Mailkube.enable_logging(device: Rails.logger)    # or your own
+```
+
+Or set `MAILKUBE_LOG`. It holds a **level**, not an on/off flag, exactly as in the python, node, Go
+and PHP SDKs: `MAILKUBE_LOG=debug` (or `trace`, or `all`) turns the SDK on, and anything more
+selective silences it — `MAILKUBE_LOG=warning` is a working way to say "logs, but not from the
+SDK". This SDK emits one class of record, the request/response trace, and that record is
+debug-level. An unrecognized value leaves logging off rather than raising, because this is read at
+`require` time.
+
+The `Authorization` and `Idempotency-Key` headers are redacted from every line, and no recipient
+address, subject or body is ever written. The response line carries the server's request id when
+one was sent.
+
+This is a duck-typed sink rather than a stdlib `Logger` on purpose: `logger` stopped being a
+default gem in Ruby 4.0, so requiring it here would break the zero-dependency claim — and a library
+has no business installing handlers on its host's behalf.
+
+## Concurrency
+
+Create one client and reuse it. It is frozen after construction and safe to share across threads,
+and across fibers where your application has installed a scheduler. Ruby releases the GVL around
+socket I/O, so plain threads give you real HTTP concurrency with no setup.
+
+Each request opens its own connection. That is deliberate: sharing one `Net::HTTP` across callers
+does not raise, it lets two callers interleave on one socket and hands one of them the other's
+response body. If you want pooling, inject an adapter that pools — and make it safe under threads
+*and* under a fiber scheduler.
+
+## Supported surface
+
+These are covered by semantic versioning:
+
+- `Mailkube.new`, `Mailkube.enable_logging`
+- `client.emails`, `client.scheduled_emails` and their verbs
+- the response models and `Mailkube::Attachment` / `Mailkube::Tag`
+- the error hierarchy and `Mailkube::ErrorName`
+- `Mailkube::Webhooks` and everything under `Mailkube::Events`
+- the `http:` adapter contract: `#call(method:, url:, headers:, body:)` returning a
+  `Mailkube::HttpResponse` and raising only `Mailkube::ConnectionError`
+
+Everything else — `Transport`, `RequestSpec`, `Config`, and the internals of `NetHttpAdapter` — is
+marked `@api private` and may change in any release. Build on the list above.
+
+### Type signatures
+
+RBS signatures ship in `sig/` and are packaged with the gem, so Steep and RBS-aware editors type
+your calls without extra setup.
+
+## More examples
+
+Runnable scripts in [`examples/`](examples/):
+
+- [`simple_send.rb`](examples/simple_send.rb) — the smallest useful program
+- [`send_with_attachments.rb`](examples/send_with_attachments.rb) — attach a file from raw bytes
+- [`send_with_tags.rb`](examples/send_with_tags.rb) — tag a send for filtering and reporting
+- [`send_with_template.rb`](examples/send_with_template.rb) — send from a saved template
+- [`schedule_send.rb`](examples/schedule_send.rb) — schedule a send, then inspect the ack
+- [`manage_scheduled_emails.rb`](examples/manage_scheduled_emails.rb) — list, paginate, retrieve,
+  reschedule and cancel
+- [`schedule_batch.rb`](examples/schedule_batch.rb) — schedule a batch, then move or cancel it as
+  a unit
+- [`webhook_receiver_sinatra.rb`](examples/webhook_receiver_sinatra.rb) — verify and dispatch
+  webhooks in Sinatra
+- [`webhook_receiver_rails.rb`](examples/webhook_receiver_rails.rb) — the same in Rails, including
+  `request.raw_post` and background dispatch
+
+## Extending this SDK
+
+Before adding a verb, a resource, a paginated listing or a webhook event, read
+[`.rules/SDK_CONTRACT.md`](.rules/SDK_CONTRACT.md) (the decisions every mailkube SDK shares) and
+[`.rules/SDK_DESIGN.md`](.rules/SDK_DESIGN.md) (how they are realized in Ruby). Both carry a
+step-by-step checklist, and every checklist ends with adding a runnable example.
+
+## Contributing
+
+See [CONTRIBUTING.md](CONTRIBUTING.md) for the development setup and the quality gates every change
+must pass. Security issues: see [SECURITY.md](SECURITY.md).
+
+## License
+
+[Apache-2.0](LICENSE) © 2026 Mailtactic, Corp.

data/lib/mailkube/client.rb

@@ -0,0 +1,52 @@
+# frozen_string_literal: true
+
+module Mailkube
+  # The API client, and this gem's composition root.
+  #
+  # Create one and reuse it. It is frozen after construction and safe to share across threads
+  # (and across fibers, where a scheduler is installed); `spec/concurrency_spec.rb` proves it
+  # rather than asserting it.
+  #
+  #     client = Mailkube.new                      # reads MAILKUBE_API_KEY
+  #     email = client.emails.send(
+  #       from: "Acme <hello@yourdomain.com>",
+  #       to: "customer@example.com",
+  #       subject: "Hello world",
+  #       html: "<p>It works!</p>"
+  #     )
+  #
+  # There are deliberately no built-in retries. A {RateLimitError} carries `retry_after` and a
+  # {ServerError} is safe to retry with backoff, so the calling application decides. Pass
+  # `idempotency_key:` to make a retry safe.
+  #
+  # This client is **synchronous**, which is the contract's sync-only case: concurrency here is
+  # the caller's concern rather than an API-surface decision. See `.rules/SDK_DESIGN.md`.
+  class Client
+    # @return [Resources::Emails] the emails namespace.
+    attr_reader :emails
+    # @return [Resources::ScheduledEmails] the scheduled-emails namespace.
+    attr_reader :scheduled_emails
+
+    # Create a client, resolving configuration from the arguments then the environment.
+    #
+    # @param api_key [String, nil] the API key; falls back to `MAILKUBE_API_KEY`.
+    # @param base_url [String, nil] the API base URL; falls back to `MAILKUBE_BASE_URL`.
+    # @param timeout [Integer, Float] the per-request open and read timeout in seconds.
+    # @param http [#call, nil] an HTTP adapter to use instead of the built-in {NetHttpAdapter}.
+    #   This is the dependency-inversion seam the test suite injects through; when supplied,
+    #   `timeout` is the adapter's business rather than this client's.
+    # @raise [ConfigurationError] when no API key is available.
+    def initialize(api_key: nil, base_url: nil, timeout: Config::DEFAULT_TIMEOUT, http: nil)
+      config = Config.new(api_key: api_key, base_url: base_url, timeout: timeout)
+      transport = Transport.new(config, http || NetHttpAdapter.new(timeout: timeout))
+
+      @config = config
+      @emails = Resources::Emails.new(transport)
+      @scheduled_emails = Resources::ScheduledEmails.new(transport)
+      freeze
+    end
+
+    # @return [String] the resolved API base URL.
+    def base_url = @config.base_url
+  end
+end