mencoro 1.0.0

data/spec/api/captures_api_spec.rb

@@ -0,0 +1,93 @@
+=begin
+#Mencoro API
+
+#Public API for Mencoro customers. Authenticate with an API key: `Authorization: Bearer mencoro_sk_...`.
+
+The version of the OpenAPI document: 1.0.0
+Contact: support@mencoro.com
+Generated by: https://openapi-generator.tech
+Generator version: 7.24.0
+
+=end
+
+require 'spec_helper'
+require 'json'
+
+# Unit tests for Mencoro::CapturesApi
+# Automatically generated by openapi-generator (https://openapi-generator.tech)
+# Please update as you see appropriate
+describe 'CapturesApi' do
+  before do
+    # run before each test
+    @api_instance = Mencoro::CapturesApi.new
+  end
+
+  after do
+    # run after each test
+  end
+
+  describe 'test an instance of CapturesApi' do
+    it 'should create an instance of CapturesApi' do
+      expect(@api_instance).to be_instance_of(Mencoro::CapturesApi)
+    end
+  end
+
+  # unit tests for list_ai_responses
+  # List captured AI answers
+  # Minimum role: viewer. Every AI answer captured for a project, newest first, one page at a time. This is the evidence under the analytics operations: the full answer text and the sources the engine cited, exactly as captured. Read `unresolved` on a citation before attributing its domain — a true value means the URL is still a redirector and the domain belongs to that redirector, not to the publisher; count the citation, do not credit the site. `passIndex` and `passCount` describe multi-pass sampling: rows sharing a `trackedQueryId` and `capturedAt` are passes of one run, not duplicates, so aggregating across them without dividing by `passCount` double-counts that run. `responseText` is the whole answer, so a page of 100 is a large response — lower `limit` rather than paging blind. Captures are kept for 16 months and purged after that; a `dateFrom` before the window is rejected rather than answered with an empty page. `total` counts every capture the filter matches, not the size of this page.
+  # @param organization_id 
+  # @param project_id 
+  # @param [Hash] opts the optional parameters
+  # @option opts [Date] :date_from Inclusive lower bound, widened to 00:00:00 UTC of the named day. Must be inside the retention window.
+  # @option opts [Date] :date_to Inclusive upper bound, widened to 23:59:59 UTC of the named day.
+  # @option opts [String] :tracked_query_id Only captures of this tracked query. Must belong to the project in the path.
+  # @option opts [Array<String>] :engines Only captures from these AI engines. Repeat the parameter or pass a comma-separated list. An empty filter means every engine.
+  # @option opts [Integer] :limit Page size. A larger value is rejected, never silently reduced.
+  # @option opts [Integer] :offset Number of captures to skip before the page starts.
+  # @option opts [String] :sort_order Direction of the capture-time ordering. An unknown value is rejected, not replaced by the default.
+  # @return [ListAiResponses200Response]
+  describe 'list_ai_responses test' do
+    it 'should work' do
+      # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
+    end
+  end
+
+  # unit tests for list_search_snapshots
+  # List captured search-results pages
+  # Minimum role: viewer. Every organic search page captured for a project, newest first, one page at a time. This is what the rank figures in the analytics operations were computed from: the ranked results as they stood at &#x60;capturedAt&#x60;, not as they stand now. Read &#x60;unresolved&#x60; on a result before attributing its domain — a true value means the URL is still a redirector and the domain belongs to that redirector; count the result, do not credit the site. &#x60;rating&#x60; and &#x60;ratingVotes&#x60; come from a rich-result star rating when Google showed one and are absent far more often than present; their absence says nothing about the page. There is no &#x60;engines&#x60; filter because every capture here comes from Google SERP. Captures are kept for 16 months and purged after that; a &#x60;dateFrom&#x60; before the window is rejected rather than answered with an empty page. &#x60;total&#x60; counts every capture the filter matches, not the size of this page.
+  # @param organization_id 
+  # @param project_id 
+  # @param [Hash] opts the optional parameters
+  # @option opts [Date] :date_from Inclusive lower bound, widened to 00:00:00 UTC of the named day. Must be inside the retention window.
+  # @option opts [Date] :date_to Inclusive upper bound, widened to 23:59:59 UTC of the named day.
+  # @option opts [String] :tracked_query_id Only captures of this tracked query. Must belong to the project in the path.
+  # @option opts [Integer] :limit Page size. A larger value is rejected, never silently reduced.
+  # @option opts [Integer] :offset Number of captures to skip before the page starts.
+  # @option opts [String] :sort_order Direction of the capture-time ordering. An unknown value is rejected, not replaced by the default.
+  # @return [ListSearchSnapshots200Response]
+  describe 'list_search_snapshots test' do
+    it 'should work' do
+      # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
+    end
+  end
+
+  # unit tests for list_shopping_snapshots
+  # List captured shopping-results pages
+  # Minimum role: viewer. Every shopping page captured for a project, newest first, one page at a time: the ranked offers as they stood at &#x60;capturedAt&#x60;. &#x60;price&#x60; and &#x60;currency&#x60; are what the seller showed at that moment — no tax normalisation, no shipping, no conversion — and two offers in one snapshot may carry different currencies, so convert before comparing. &#x60;productId&#x60; is the marketplace&#39;s own identifier for the listing, stable enough to follow one offer across snapshots, and it is not a Mencoro id. Offers turn over far faster than organic results, so two snapshots days apart routinely share none; that is the marketplace behaving normally, not a gap in the capture. Unlike organic results, a shopping offer carries no &#x60;unresolved&#x60; flag: the capture pipeline does not record one for this surface. Shopping captures are trimmed by the same raw-data purge as AI answers and search pages, so the same retention floor applies: a &#x60;dateFrom&#x60; before it is refused rather than answered with an empty page. &#x60;total&#x60; counts every capture the filter matches, not the size of this page.
+  # @param organization_id 
+  # @param project_id 
+  # @param [Hash] opts the optional parameters
+  # @option opts [Date] :date_from Inclusive lower bound, widened to 00:00:00 UTC of the named day. A date before the retention floor is refused rather than answered with an empty page: shopping captures are aged out by the raw-data purge like every other capture.
+  # @option opts [Date] :date_to Inclusive upper bound, widened to 23:59:59 UTC of the named day.
+  # @option opts [String] :tracked_query_id Only captures of this tracked query. Must belong to the project in the path.
+  # @option opts [Integer] :limit Page size. A larger value is rejected, never silently reduced.
+  # @option opts [Integer] :offset Number of captures to skip before the page starts.
+  # @option opts [String] :sort_order Direction of the capture-time ordering. An unknown value is rejected, not replaced by the default.
+  # @return [ListShoppingSnapshots200Response]
+  describe 'list_shopping_snapshots test' do
+    it 'should work' do
+      # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
+    end
+  end
+
+end

data/spec/api/clusters_api_spec.rb

@@ -0,0 +1,126 @@
+=begin
+#Mencoro API
+
+#Public API for Mencoro customers. Authenticate with an API key: `Authorization: Bearer mencoro_sk_...`.
+
+The version of the OpenAPI document: 1.0.0
+Contact: support@mencoro.com
+Generated by: https://openapi-generator.tech
+Generator version: 7.24.0
+
+=end
+
+require 'spec_helper'
+require 'json'
+
+# Unit tests for Mencoro::ClustersApi
+# Automatically generated by openapi-generator (https://openapi-generator.tech)
+# Please update as you see appropriate
+describe 'ClustersApi' do
+  before do
+    # run before each test
+    @api_instance = Mencoro::ClustersApi.new
+  end
+
+  after do
+    # run after each test
+  end
+
+  describe 'test an instance of ClustersApi' do
+    it 'should create an instance of ClustersApi' do
+      expect(@api_instance).to be_instance_of(Mencoro::ClustersApi)
+    end
+  end
+
+  # unit tests for apply_clustering_job
+  # Apply the result of a clustering job
+  # Minimum role: manager. Writes a completed clustering job onto the tracked queries it was computed for: it creates the clusters the job proposed that the project does not have yet, then assigns each tracked query according to the merge mode the job was started with — fill_gaps leaves already grouped queries alone, add_on_top only adds, full_regroup replaces a query's clusters with the proposed set and therefore REMOVES clusters that are not in it — but only for a tracked query the job actually returned an assignment for. A tracked query the job was started over and produced no assignment for is listed under `unassigned` and left exactly as it was, under every mode; it is not treated as \"belongs to no cluster\" and is never stripped. That matters most with restrictToExistingClusters, where the model is expected to return nothing for queries that fit no existing cluster. The body must be empty: the assignments, the target tracked queries and the mode all come from the job, so this call cannot apply something the job did not produce. Synchronous and partially successful — always 200, with each tracked query under `successful` or `failed`, and nothing rolled back because one failed. A job that is not completed, or one that produced no assignments, is refused with 409. Requires the write capability and an Idempotency-Key header; repeating the key returns the first answer rather than applying twice.
+  # @param organization_id 
+  # @param project_id 
+  # @param job_id Must be a clustering job started for this organization and project.
+  # @param idempotency_key Repeat it to retry a lost response without applying the job twice.
+  # @param [Hash] opts the optional parameters
+  # @return [ApplyClusteringJobOutcome]
+  describe 'apply_clustering_job test' do
+    it 'should work' do
+      # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
+    end
+  end
+
+  # unit tests for batch_create_query_clusters
+  # Create several keyword clusters at once
+  # Minimum role: manager. Creates up to 100 empty keyword clusters in one call. Names are trimmed and lower-cased and repeated names in the body are collapsed before anything is written. Partial success: the answer is always 200 and reports every name under `successful` or under `failed` — a name already taken in the project fails with query_cluster_name_already_exists and is NOT resolved to the existing cluster, while the other names are still created. Nothing is rolled back because one name failed. The clusters are created empty; no tracked query is assigned to them. The organization must not be archived; an archived project IS refused with 409, stricter than the Mencoro app, which lets cluster writes into one. Requires the write capability and an Idempotency-Key header.
+  # @param organization_id 
+  # @param project_id 
+  # @param idempotency_key Repeat it to retry a lost response without creating the batch twice.
+  # @param batch_create_query_clusters_request_data 
+  # @param [Hash] opts the optional parameters
+  # @return [BatchCreateQueryClustersOutcome]
+  describe 'batch_create_query_clusters test' do
+    it 'should work' do
+      # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
+    end
+  end
+
+  # unit tests for create_query_cluster
+  # Create a keyword cluster
+  # Minimum role: manager. Creates one empty keyword cluster in the project. The name is trimmed and lower-cased before it is stored, and it must be unique within the project: a name that already exists is refused with 409 and nothing is merged into the existing cluster. The cluster starts with no tracked queries in it — this operation does not assign anything to it. The organization must not be archived; an archived project IS refused with 409, stricter than the Mencoro app, which lets cluster writes into one. Requires the write capability and an Idempotency-Key header.
+  # @param organization_id 
+  # @param project_id 
+  # @param idempotency_key A token you choose per operation, 8 to 255 printable ASCII characters with no spaces; a UUID is the obvious choice. Repeat it to retry a lost response without creating a second cluster. The key is scoped to your API key, and it is bound to the method, the path and the body of the first attempt: repeating it with anything else changed is refused with 409 rather than replayed.
+  # @param create_query_cluster_request 
+  # @param [Hash] opts the optional parameters
+  # @return [QueryClusterResource]
+  describe 'create_query_cluster test' do
+    it 'should work' do
+      # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
+    end
+  end
+
+  # unit tests for delete_query_cluster
+  # Delete a keyword cluster
+  # Minimum role: manager. Deletes one keyword cluster. The tracked queries that were in it are NOT deleted: they are unassigned from this cluster and keep every other cluster they belong to. Analytics filtered by this cluster id return nothing afterwards, including for dates before the deletion, because that filter reads current membership. This cannot be undone — recreating a cluster with the same name produces a new id and an empty cluster. The organization must not be archived, and neither must the project: an archived project IS refused with 409, stricter than the Mencoro app, which lets cluster writes into one. Requires the write capability and an Idempotency-Key header.
+  # @param organization_id 
+  # @param project_id 
+  # @param cluster_id Must be a cluster of the project in the path.
+  # @param idempotency_key Repeat it to retry a lost response; a fresh key answers 404 once the cluster is gone.
+  # @param [Hash] opts the optional parameters
+  # @return [DeleteQueryCluster200Response]
+  describe 'delete_query_cluster test' do
+    it 'should work' do
+      # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
+    end
+  end
+
+  # unit tests for rename_query_cluster
+  # Rename a keyword cluster
+  # Minimum role: manager. Changes the name of one keyword cluster and nothing else: the tracked queries assigned to it are untouched, and its id does not change, so nothing a client stored breaks. The new name is trimmed and lower-cased and must be unique within the project; a collision is refused with 409. Renaming to the name the cluster already has is accepted and is a no-op. The organization must not be archived; an archived project IS refused with 409, stricter than the Mencoro app, which lets cluster writes into one. Requires the write capability and an Idempotency-Key header.
+  # @param organization_id 
+  # @param project_id 
+  # @param cluster_id Must be a cluster of the project in the path.
+  # @param idempotency_key Repeat it to retry a lost response without renaming twice.
+  # @param create_query_cluster_request 
+  # @param [Hash] opts the optional parameters
+  # @return [QueryClusterResource]
+  describe 'rename_query_cluster test' do
+    it 'should work' do
+      # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
+    end
+  end
+
+  # unit tests for start_clustering_job
+  # Start a keyword clustering job
+  # Minimum role: manager. Asks the clustering service to propose keyword clusters for up to 500 tracked queries of the project, and answers 202 with the job to poll — the work runs in the background and a 202 says it was accepted, never that it succeeded. THE JOB WRITES NOTHING: it produces a proposal, and nothing changes until it is applied through the apply operation, which is a separate call. Duplicate query texts within the selection are sent once. Requires an entitled subscription (402 otherwise) and the organization must be active and the project not archived. Rate limited to 10 starts per minute per organization, shared with the same operation in the web application. Requires the write capability and an Idempotency-Key header; repeating the key returns the first job rather than starting a second.
+  # @param organization_id 
+  # @param project_id 
+  # @param idempotency_key Repeat it to retry a lost response without starting a second job.
+  # @param start_clustering_job_request_data 
+  # @param [Hash] opts the optional parameters
+  # @return [AcceptedJobResource]
+  describe 'start_clustering_job test' do
+    it 'should work' do
+      # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
+    end
+  end
+
+end

data/spec/api/discovery_api_spec.rb

@@ -0,0 +1,94 @@
+=begin
+#Mencoro API
+
+#Public API for Mencoro customers. Authenticate with an API key: `Authorization: Bearer mencoro_sk_...`.
+
+The version of the OpenAPI document: 1.0.0
+Contact: support@mencoro.com
+Generated by: https://openapi-generator.tech
+Generator version: 7.24.0
+
+=end
+
+require 'spec_helper'
+require 'json'
+
+# Unit tests for Mencoro::DiscoveryApi
+# Automatically generated by openapi-generator (https://openapi-generator.tech)
+# Please update as you see appropriate
+describe 'DiscoveryApi' do
+  before do
+    # run before each test
+    @api_instance = Mencoro::DiscoveryApi.new
+  end
+
+  after do
+    # run after each test
+  end
+
+  describe 'test an instance of DiscoveryApi' do
+    it 'should create an instance of DiscoveryApi' do
+      expect(@api_instance).to be_instance_of(Mencoro::DiscoveryApi)
+    end
+  end
+
+  # unit tests for start_brand_discovery_job
+  # Start a brand discovery job for a project
+  # Minimum role: manager. Starts background discovery of the brands and competitors around a project and answers 202 with the job to poll; it never returns brands inline. The job PROPOSES names: it creates and updates nothing, so neither the brand profile nor the competitor list changes because this endpoint was called. The organization must be active. Unlike keyword and prompt discovery this operation does not require an entitled subscription, matching the application behaviour it mirrors. Ten starts per minute per organization, counted across every key of every member and shared with the same operation in the Mencoro app; a retry carrying an Idempotency-Key already answered is served from the record and does not count. A project whose brand monitoring profile has not been created yet is still accepted and still billed: the job runs grounded on the project name alone, with no website domains, brand names or competitors to work from, and completes normally. Configure the brand profile first if you want the discovery grounded.
+  # @param organization_id 
+  # @param project_id Must belong to the organization in the path.
+  # @param idempotency_key Repeat it to retry a start whose response was lost; the same key returns the same job instead of starting a second one.
+  # @param [Hash] opts the optional parameters
+  # @option opts [StartBrandDiscoveryJobRequest] :start_brand_discovery_job_request 
+  # @return [AcceptedJobResource]
+  describe 'start_brand_discovery_job test' do
+    it 'should work' do
+      # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
+    end
+  end
+
+  # unit tests for start_brand_name_suggestion_job
+  # Start a brand-name alias suggestion job
+  # Minimum role: manager. Starts a background, web-search-grounded job that suggests alias spellings for one entity - a brand, a project or a competitor - described entirely by the body, and answers 202 with the job to poll; it never returns suggestions inline. The entity need not exist: nothing is looked up, nothing is attached and nothing is saved, so the suggestions are the caller's to apply. Names sent in `enteredBrandNames` are excluded from the result. The organization must be active; no subscription is required, matching the application behaviour this mirrors. Ten starts per minute per organization, counted across every key of every member; a retry carrying an Idempotency-Key already answered is served from the record and does not count.
+  # @param organization_id 
+  # @param idempotency_key Repeat it to retry a start whose response was lost; the same key returns the same job instead of starting a second one.
+  # @param start_brand_name_suggestion_job_request 
+  # @param [Hash] opts the optional parameters
+  # @return [AcceptedJobResource]
+  describe 'start_brand_name_suggestion_job test' do
+    it 'should work' do
+      # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
+    end
+  end
+
+  # unit tests for start_keyword_discovery_job
+  # Start a keyword discovery job for a project
+  # Minimum role: manager. Starts background keyword discovery from free-text seed input and answers 202 with the job to poll; it never returns keywords inline. The job SUGGESTS keywords - it creates no tracked queries and changes nothing in the project, so a completed job is a list to choose from, not work that has been applied. Queries the project already tracks are excluded from the suggestions automatically; `excludeQueries` adds more on top for this run only. The organization must be active and hold an entitled subscription, because the run spends provider budget. Ten starts per minute per organization, counted across every key of every member; a retry carrying an Idempotency-Key already answered is served from the record and does not count. Run tuning is not exposed: the discovery fan-out uses provider defaults.
+  # @param organization_id 
+  # @param project_id Must belong to the organization in the path.
+  # @param idempotency_key Repeat it to retry a start whose response was lost; the same key returns the same job instead of starting a second one.
+  # @param start_keyword_discovery_job_request 
+  # @param [Hash] opts the optional parameters
+  # @return [AcceptedJobResource]
+  describe 'start_keyword_discovery_job test' do
+    it 'should work' do
+      # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
+    end
+  end
+
+  # unit tests for start_prompt_discovery_job
+  # Start a geo prompt discovery job for a project
+  # Minimum role: manager. Starts background discovery of natural-language prompts - the questions an answer engine gets asked - from free-text seed input, and answers 202 with the job to poll; it never returns prompts inline. The job SUGGESTS prompts: it creates no tracked queries and changes nothing in the project. `country` is required here, unlike keyword discovery, because a prompt is a question asked from somewhere and the provider request has no default for it. Queries the project already tracks are excluded automatically; `excludeQueries` adds more for this run only. The organization must be active and hold an entitled subscription, because the run spends provider budget. Ten starts per minute per organization, counted across every key of every member; a retry carrying an Idempotency-Key already answered is served from the record and does not count. Run tuning is not exposed: the discovery fan-out uses provider defaults.
+  # @param organization_id 
+  # @param project_id Must belong to the organization in the path.
+  # @param idempotency_key Repeat it to retry a start whose response was lost; the same key returns the same job instead of starting a second one.
+  # @param start_prompt_discovery_job_request 
+  # @param [Hash] opts the optional parameters
+  # @return [AcceptedJobResource]
+  describe 'start_prompt_discovery_job test' do
+    it 'should work' do
+      # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
+    end
+  end
+
+end

data/spec/api/invitations_api_spec.rb

@@ -0,0 +1,83 @@
+=begin
+#Mencoro API
+
+#Public API for Mencoro customers. Authenticate with an API key: `Authorization: Bearer mencoro_sk_...`.
+
+The version of the OpenAPI document: 1.0.0
+Contact: support@mencoro.com
+Generated by: https://openapi-generator.tech
+Generator version: 7.24.0
+
+=end
+
+require 'spec_helper'
+require 'json'
+
+# Unit tests for Mencoro::InvitationsApi
+# Automatically generated by openapi-generator (https://openapi-generator.tech)
+# Please update as you see appropriate
+describe 'InvitationsApi' do
+  before do
+    # run before each test
+    @api_instance = Mencoro::InvitationsApi.new
+  end
+
+  after do
+    # run after each test
+  end
+
+  describe 'test an instance of InvitationsApi' do
+    it 'should create an instance of InvitationsApi' do
+      expect(@api_instance).to be_instance_of(Mencoro::InvitationsApi)
+    end
+  end
+
+  # unit tests for cancel_invitation
+  # Cancel a pending invitation
+  # Minimum role: owner. The link already emailed to the invitee stops working. Only a pending invitation can be cancelled; one that was accepted, rejected or has expired is refused.
+  # @param organization_id 
+  # @param invitation_id 
+  # @param x_mencoro_confirmation 
+  # @param idempotency_key 
+  # @param [Hash] opts the optional parameters
+  # @return [InvitationResource]
+  describe 'cancel_invitation test' do
+    it 'should work' do
+      # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
+    end
+  end
+
+  # unit tests for create_invitation
+  # Invite somebody to an organization
+  # Minimum role: owner. Sends an invitation email that expires after 14 days. If the address already belongs to an active member the call succeeds and creates nothing - answered as 200 with created=false rather than 201, so a client can tell the two apart. Preview it first; the preview says which of the two will happen.
+  # @param organization_id 
+  # @param x_mencoro_confirmation 
+  # @param idempotency_key 
+  # @param create_invitation_request 
+  # @param [Hash] opts the optional parameters
+  # @return [CreateInvitation200Response]
+  describe 'create_invitation test' do
+    it 'should work' do
+      # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
+    end
+  end
+
+  # unit tests for list_invitations
+  # List an organization's invitations
+  # Minimum role: owner. Returns the invitations issued for this organization, in every state. The invitation token is never returned. `status` matches the stored state, so an invitation that has passed its `expiresAt` is still listed as pending until it is transitioned; compare `expiresAt` to decide. Rows are ordered by the chosen sort field, and invitations sharing the same value keep no guaranteed relative order across pages.Send `Accept: text/csv` to receive the same page as a CSV download instead of JSON: same filters, same authorization, same page window and the same maximum of 100 rows — it is this page in another format, not a bulk export, so a whole collection is still read by paging. The CSV carries no `total`, because a table whose every row is a record has nowhere to put one; read it from the JSON representation of the same request. Cells beginning with `=`, `+`, `-` or `@` are prefixed with an apostrophe so a spreadsheet treats them as text rather than running them as formulas.
+  # @param organization_id 
+  # @param [Hash] opts the optional parameters
+  # @option opts [Integer] :limit 
+  # @option opts [Integer] :offset 
+  # @option opts [String] :search Matches part of the invited email address.
+  # @option opts [String] :status Absent means every state.
+  # @option opts [String] :sort_by 
+  # @option opts [String] :sort_order 
+  # @return [ListInvitations200Response]
+  describe 'list_invitations test' do
+    it 'should work' do
+      # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
+    end
+  end
+
+end

data/spec/api/jobs_api_spec.rb

@@ -0,0 +1,48 @@
+=begin
+#Mencoro API
+
+#Public API for Mencoro customers. Authenticate with an API key: `Authorization: Bearer mencoro_sk_...`.
+
+The version of the OpenAPI document: 1.0.0
+Contact: support@mencoro.com
+Generated by: https://openapi-generator.tech
+Generator version: 7.24.0
+
+=end
+
+require 'spec_helper'
+require 'json'
+
+# Unit tests for Mencoro::JobsApi
+# Automatically generated by openapi-generator (https://openapi-generator.tech)
+# Please update as you see appropriate
+describe 'JobsApi' do
+  before do
+    # run before each test
+    @api_instance = Mencoro::JobsApi.new
+  end
+
+  after do
+    # run after each test
+  end
+
+  describe 'test an instance of JobsApi' do
+    it 'should create an instance of JobsApi' do
+      expect(@api_instance).to be_instance_of(Mencoro::JobsApi)
+    end
+  end
+
+  # unit tests for get_async_job
+  # Get an asynchronous job
+  # Minimum role: manager. The status of one asynchronous job started inside this organization — geo prompt discovery, keyword discovery, query clustering, brand discovery or brand-name suggestion — and, once it has completed, its result. Poll it until `status` is terminal: `completed` or `failed`. A null `result` means the result is not known, either because the job is still in flight or because it failed; it never means the job produced an empty result. A failed job carries no reason: the stored one is an internal exception message, not a published field. A job started by another organization, a job of a type this API does not publish, and a job id that does not exist all answer 404 alike, so the API never confirms that an inaccessible job exists.
+  # @param organization_id 
+  # @param job_id Must be a job started inside the organization in the path.
+  # @param [Hash] opts the optional parameters
+  # @return [AsyncJobResource]
+  describe 'get_async_job test' do
+    it 'should work' do
+      # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
+    end
+  end
+
+end

data/spec/api/members_api_spec.rb

@@ -0,0 +1,111 @@
+=begin
+#Mencoro API
+
+#Public API for Mencoro customers. Authenticate with an API key: `Authorization: Bearer mencoro_sk_...`.
+
+The version of the OpenAPI document: 1.0.0
+Contact: support@mencoro.com
+Generated by: https://openapi-generator.tech
+Generator version: 7.24.0
+
+=end
+
+require 'spec_helper'
+require 'json'
+
+# Unit tests for Mencoro::MembersApi
+# Automatically generated by openapi-generator (https://openapi-generator.tech)
+# Please update as you see appropriate
+describe 'MembersApi' do
+  before do
+    # run before each test
+    @api_instance = Mencoro::MembersApi.new
+  end
+
+  after do
+    # run after each test
+  end
+
+  describe 'test an instance of MembersApi' do
+    it 'should create an instance of MembersApi' do
+      expect(@api_instance).to be_instance_of(Mencoro::MembersApi)
+    end
+  end
+
+  # unit tests for change_member_role
+  # Change a member role
+  # Minimum role: owner. The role of a suspended member cannot be changed, and the last active owner cannot be demoted. Preview it first: the confirmation is bound to the number of active owners, so another owner being suspended in between invalidates it rather than stranding the organization.
+  # @param organization_id 
+  # @param member_id 
+  # @param x_mencoro_confirmation 
+  # @param idempotency_key 
+  # @param change_member_role_request 
+  # @param [Hash] opts the optional parameters
+  # @return [MemberResource]
+  describe 'change_member_role test' do
+    it 'should work' do
+      # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
+    end
+  end
+
+  # unit tests for get_member
+  # Get one organization membership
+  # Minimum role: owner — the same floor the members listing enforces, because a caller who can page the roster has already seen this record. Returns the facts of one membership: its role, whether it is active or suspended, and when it was joined. It does NOT describe the person behind it: no name, no email address, no phone number and no profile image, so a membership id can never be turned into a contact lookup. The membership is read from PostgreSQL, the same row at the same freshness the listing publishes. A membership belonging to another organization answers 404, exactly as an unknown or malformed id does, so the API never confirms that an inaccessible membership exists; the one 403 is a key without the read capability. The response carries no organizationId — it is the one in the path — and no creation timestamp; joinedAt is the membership fact. No query parameters are accepted.
+  # @param organization_id 
+  # @param member_id The membership id, not the user id. Must belong to the organization in the path.
+  # @param [Hash] opts the optional parameters
+  # @return [MemberResource]
+  describe 'get_member test' do
+    it 'should work' do
+      # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
+    end
+  end
+
+  # unit tests for list_members
+  # List an organization's members
+  # Minimum role: owner. The application exposes this roster twice and the two disagree — its member screen shows it to any viewer, while its non-BFF endpoint requires an owner — so the published API takes the stricter of the two and requires an owner. A membership describes the membership, not the person: names and email addresses are never returned here, and there is no search parameter, because both would turn the roster into a contact export. Omitting \"status\" returns active and suspended memberships alike. Sorting by \"role\" is alphabetical on the role name, not by seniority.Send `Accept: text/csv` to receive the same page as a CSV download instead of JSON: same filters, same authorization, same page window and the same maximum of 100 rows — it is this page in another format, not a bulk export, so a whole collection is still read by paging. The CSV carries no `total`, because a table whose every row is a record has nowhere to put one; read it from the JSON representation of the same request. Cells beginning with `=`, `+`, `-` or `@` are prefixed with an apostrophe so a spreadsheet treats them as text rather than running them as formulas.
+  # @param organization_id 
+  # @param [Hash] opts the optional parameters
+  # @option opts [Integer] :limit 
+  # @option opts [Integer] :offset 
+  # @option opts [String] :status Absent means both states.
+  # @option opts [String] :sort_by 
+  # @option opts [String] :sort_order 
+  # @return [ListMembers200Response]
+  describe 'list_members test' do
+    it 'should work' do
+      # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
+    end
+  end
+
+  # unit tests for reactivate_member
+  # Reactivate a suspended member
+  # Minimum role: owner. The member keeps the role they had and regains access on their very next request. A member who is already active cannot be reactivated.
+  # @param organization_id 
+  # @param member_id 
+  # @param x_mencoro_confirmation 
+  # @param idempotency_key 
+  # @param [Hash] opts the optional parameters
+  # @return [MemberResource]
+  describe 'reactivate_member test' do
+    it 'should work' do
+      # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
+    end
+  end
+
+  # unit tests for suspend_member
+  # Suspend a member
+  # Minimum role: owner. The member loses access on their very next request, including through any API key they own that is scoped to this organization. The last active owner cannot be suspended.
+  # @param organization_id 
+  # @param member_id 
+  # @param x_mencoro_confirmation 
+  # @param idempotency_key 
+  # @param [Hash] opts the optional parameters
+  # @return [MemberResource]
+  describe 'suspend_member test' do
+    it 'should work' do
+      # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
+    end
+  end
+
+end

data/spec/api/organization_operations_api_spec.rb

@@ -0,0 +1,47 @@
+=begin
+#Mencoro API
+
+#Public API for Mencoro customers. Authenticate with an API key: `Authorization: Bearer mencoro_sk_...`.
+
+The version of the OpenAPI document: 1.0.0
+Contact: support@mencoro.com
+Generated by: https://openapi-generator.tech
+Generator version: 7.24.0
+
+=end
+
+require 'spec_helper'
+require 'json'
+
+# Unit tests for Mencoro::OrganizationOperationsApi
+# Automatically generated by openapi-generator (https://openapi-generator.tech)
+# Please update as you see appropriate
+describe 'OrganizationOperationsApi' do
+  before do
+    # run before each test
+    @api_instance = Mencoro::OrganizationOperationsApi.new
+  end
+
+  after do
+    # run after each test
+  end
+
+  describe 'test an instance of OrganizationOperationsApi' do
+    it 'should create an instance of OrganizationOperationsApi' do
+      expect(@api_instance).to be_instance_of(Mencoro::OrganizationOperationsApi)
+    end
+  end
+
+  # unit tests for preview_organization_operation
+  # Preview an organization operation and obtain a confirmation
+  # Organization, member and invitation changes need two calls. This one reports the concrete changes, the side effects, the warnings and the conditions, and returns a confirmation valid for five minutes. Send it back in the X-Mencoro-Confirmation header, together with an Idempotency-Key, on the call that performs the operation. Previewing has no effects of any kind.
+  # @param preview_organization_operation_request 
+  # @param [Hash] opts the optional parameters
+  # @return [PreviewOrganizationOperation200Response]
+  describe 'preview_organization_operation test' do
+    it 'should work' do
+      # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
+    end
+  end
+
+end