How to Use RPVS ownership and deregistration changes in Muse Code
Returns dated beneficial-owner changes or partner deregistrations from Slovakia's RPVS register. Use it to review changes between full register snapshots.
Prompts to try with RPVS ownership and deregistration changes in Muse Code
Copy an example into Muse Code, or ask in your own words.
Use RPVS ownership and deregistration changes to retrieve available ownership changes in Slovakia's register and compare the affected company identifiers with our supplier dataset.
Use RPVS ownership and deregistration changes to look this up and give me the result as a table. Save the result in ./assets.
Pull the latest numbers from RPVS ownership and deregistration changes and tell me what changed since last week.
Check RPVS ownership and deregistration changes and summarize what you find in three bullet points.
Pull the newest data from RPVS ownership and deregistration changes and give me the result as a table.
How to set up RPVS ownership and deregistration changes in Muse Code
Pick the way that suits you. Each takes about two minutes.
Use Spiral's MCP server
- Install Muse Code
curl -fsSL https://dev.meta.ai/install.sh | bash
- Ask Muse to add the server
Start muse and ask:
Add the Spiral MCP server at https://api.spiral.ai/mcp
- Sign in
In your terminal, run:
muse mcp login spiral
Use the Spiral skill
- Send Muse Code this message
Your agent reads Spiral's skill and sets itself up.
set up https://spiral.ai/SKILL.md
- Sign in or paste a key
Approve Spiral in the browser, or give the agent a key from the console.
Use the Spiral CLI
- Install and sign in
Installs the Spiral CLI, signs you in and adds its skill to your coding agents.
npx -y spiral-cli@latest init
Call the Spiral API
- Create an API key
In the console, under API keys.
- Run RPVS ownership and deregistration changes
One request; the result comes back by polling or a webhook.
curl https://api.spiral.ai/v1/runs \ -H "Authorization: Bearer $SPIRAL_API_KEY" \ -H "Content-Type: application/json" \ -H "Idempotency-Key: $(uuidgen)" \ -d '{ "provider": "alexandria", "model": "rpvs-gov-sk/beneficial-owners/records_changes", "input": { "since": "<since>" } }'
Then paste one of the prompts above: Muse Code finds RPVS ownership and deregistration changes on Spiral, shows the price and runs it.
RPVS ownership and deregistration changes providers and prices
Spiral runs RPVS ownership and deregistration changes through Alexandria. Open a card for today's price, with every fee included.
Settings you can ask for
Ask Muse Code for any of these in your prompt.
| Setting | Allowed values | Default | Description |
|---|---|---|---|
| Stream | owners or deregistrations | owners | stream |
| Max pages | 1 to 20 | 5 | max_pages |
| Include birth date | on or off | Also return the full |
Every API field of RPVS (Slovak Register of Public Sector Partners) · Records changes is on its tool page: open its card above.
What can you do with RPVS ownership and deregistration changes in Muse Code?
Build a supplier review table that links company identifiers to registered ownership history. A coding agent can match your procurement dataset to RPVS records and add comparisons between collection runs.
Maintain a supplier ownership review
Resolve supplier names, inspect company ownership records, and establish a register snapshot. Compare register status and collect subsequent ownership changes or deregistrations for procurement review.
Prepare contract renewal reviews
Match renewing contractors to their RPVS entries and compare their ownership records with an earlier register snapshot. Use status checks and dated changes to identify companies that need another review before renewal.
Review registered grant recipients
Match a public list of corporate grant recipients to RPVS company records and retain a register baseline. Follow ownership changes and deregistrations, using register status to inform collection checks.
Follow companies in public-contract reporting
Resolve the business names appearing in public-contract reporting, examine their registered ownership histories, and build a comparison dataset. Check register status and dated changes to prepare follow-up research on those companies.
Build an ownership chronology
Arrange a registered company's beneficial-owner history by its published dates. Compare subsequent dated changes with the company record to prepare a chronology for a business review.
Check a register collection process
Compare source status before and after a full register collection. Review dated ownership changes alongside the collected snapshot to identify records worth fetching again.
More on RPVS ownership and deregistration changes and Muse Code
Overview
RPVS ownership and deregistration changes in other agents
Questions about RPVS ownership and deregistration changes in Muse Code
Can Muse Code use RPVS ownership and deregistration changes?
Yes. Add Spiral to Muse Code as an MCP server, and Muse Code can find and run RPVS ownership and deregistration changes like any built-in tool.
How much does RPVS ownership and deregistration changes cost in Muse Code?
$0.00873 per call. You pay from your Spiral balance as you go, with no subscription, and a failed run is not charged. Your Muse Code plan is separate.
Do I need an Alexandria account to use RPVS ownership and deregistration changes in Muse Code?
No. Spiral runs RPVS ownership and deregistration changes on its own Alexandria account. You sign in to Spiral once and never paste a key.
How long does it take to set up RPVS ownership and deregistration changes in Muse Code?
About two minutes: install Muse Code, then ask Muse to add the server, then sign in.
Does Muse Code wait while RPVS ownership and deregistration changes runs?
RPVS ownership and deregistration changes runs in the background. Muse Code starts the run, checks on it and gives you the json when it's ready.
Does RPVS cover every Slovak company?
No. Its coverage centers on registered public-sector partners, including recipients of public funds or assets above statutory thresholds. An unsuccessful search does not establish that a business does not exist.
How fresh is the ownership information?
RPVS reflects registered information rather than immediate knowledge of business events. The ministry's FAQ describes a 60-day notification period for beneficial-owner changes, and annual verification establishes the position on December 31.
Who is responsible for ownership accuracy?
The public-sector partner and its authorized representative bear responsibility for registered ownership information. The official data model also includes a beneficial-owner verification date, which gives useful context for reviewing a company record.
Does RPVS include historical ownership information?
Alexandria documents company identity versions and dated beneficial-owner history from RPVS. This supports examining recorded ownership periods as well as a company's current entry.
Which business details are public?
The public register displays company registration numbers, legal forms, addresses, registration status, authorized representatives, and registration and removal dates. Its public information therefore extends beyond a company name and an ownership list.
Start using RPVS ownership and deregistration changes in Muse Code
One Spiral account for every tool your agent needs. No subscription; you pay per run.
Paste this into Muse Code:
set up https://spiral.ai/SKILL.md


