Sanaf AI
Start free
Developer Tools

Blazemeter, worked by an AI employee

Not another app for your team to learn, and not a set of rules for you to build. You hire an AI employee, you give it access to your Blazemeter account, and you ask it for things in Slack or Teams the way you would ask anyone else on the team. There is nothing to map and nothing to maintain.

  • Developer Tools
  • Connects with a key
  • 20 ready-made tools
  • Asked in Slack or Teams
At work

An illustration of how the conversation reads, not a transcript from a client account.

What Blazemeter is

BlazeMeter is a continuous testing platform that enables users to create, run, and analyze performance and functional tests for web and mobile applications.

You paste in a key from your own Blazemeter account. It is kept encrypted, and you can withdraw it from inside Blazemeter whenever you like.

How a run works

One message in, the work done in Blazemeter.

  1. 01

    You ask

    You message your AI employee in the chat your team already has open, in one sentence, in your own words.

  2. 02

    It works out the step

    It decides what the job needs in Blazemeter. You do not pick anything from a menu or wire anything together.

  3. 03

    It does the work

    Signed in to your own Blazemeter account, inside the access you granted it, doing the thing you asked for.

  4. 04

    It reports back

    It tells you what it did, in the same thread. If it could not do something, it says so rather than guessing.

20 tools it already has

What it can do in Blazemeter

These are the ready-made tools your AI employee already has in Blazemeter. It is not limited to them, but it never has to be taught these.

  • Create API Monitoring ScheduleTool to create a new schedule for running api monitoring tests. use when you need to automate test runs at defined intervals after determining the correct cron expression and test
  • Create Multi TestTool to create a new multi-test within a specified project. use after confirming the project id. example: "create a multi-test named 'load-test' in project 12345."
  • Create ProjectTool to create a new project. use when you need to initialize a project in a specific workspace. use after confirming the workspace id.
  • Create TestTool to create a new single test within a specified project. use when registering a new performance test via api.
  • Delete API Monitoring ScheduleTool to delete a specific test schedule by its id. use when you need to remove a scheduled test by its unique schedule identifier.
  • Get AccountsTool to retrieve a list of accounts associated with the authenticated user. use after confirming valid authentication.
  • Get API Monitoring ScheduleTool to retrieve details of a specific api monitoring schedule by its id. use when you need to inspect the configuration or timing of an existing schedule.
  • Get API Monitoring SchedulesTool to retrieve a list of all test schedules in your account. use when you need to enumerate existing schedules to manage or review them.
  • Get Multi TestTool to retrieve details of a specific multi-test. use after creating or listing multi-tests when you need full configuration and status. minimal example: "get multi-test 12345678
  • Get Multi TestsTool to retrieve a list of multi-tests within a specified project or workspace. use when you need to enumerate available multi-tests by specifying a project or workspace id.
  • Get ProjectsTool to retrieve a list of projects within a specified workspace. use when you need to enumerate or page through projects under a given workspace.
  • Get Test ValidationsTool to retrieve validation results for a specific test by its id. use after uploading or modifying test files to confirm file validation status.
  • Get TestsTool to retrieve a list of single tests within a specified project or workspace. use when you need to list tests after organizing them. example: "get tests for projectid=prj-5678".
  • Get UserTool to retrieve information about the authenticated user. use when you need the current user's profile and have valid authentication.
  • Get WorkspacesTool to retrieve a list of workspaces for a specified account. use when you need to list or filter workspaces by account, status, or name.
  • Stop MasterTool to stop a specific test execution (master) by its id. use when you need to abort a running test.
  • Update API Monitoring ScheduleTool to update the configuration of an existing api monitoring schedule. use when you need to enable or disable a schedule after confirming its id.
  • Update TestTool to update details of a specific test by its id. use when you need to modify test configuration or name of an existing test after confirming its id. example: "update the test n
  • Upload Test FilesTool to upload files to a specific test by its id. use after creating or selecting a test to attach scripts or resources before execution.
  • Validate TestTool to validate a specific test by its id. use after creating or updating a test to ensure its configuration is valid.
Access, and who is in charge of it

You stay the boss of your Blazemeter account.

Nothing connects until you approve it. You grant access one app at a time, you can take it back the same way, and everything your AI employee does in there is written down where you can see it.

How we handle your data
  • It signs in to your own Blazemeter account. You are not moving anything into ours.
  • You grant access one app at a time, and you can take it back the same way.
  • Everything it does in Blazemeter is written down, with what it did and when.
  • Anything you tell it to check with you first, it checks with you first.
Other apps in the same corner of the business

It works in Blazemeter and the rest of your software in the same job

A real job rarely stays in one place. Reading a message in one app, checking a record in another and writing the result in a third is one request to your AI employee, not three.

See every app

Questions people ask about Blazemeter

Can an AI employee really work inside Blazemeter?
Yes. It signs in to your own Blazemeter account and works in it the way a new hire would, from the chat your team already has open. Nobody installs anything, and nobody learns a new screen.
Do I have to move anything out of Blazemeter?
No. Nothing moves and nothing is replaced. Your records stay in Blazemeter, your team carries on in the same screens they used yesterday, and your AI employee works alongside them in there.
How does it get into my Blazemeter account?
You paste in a key from your own Blazemeter account. It is kept encrypted, and you can withdraw it from inside Blazemeter whenever you like. You approve it before anything connects, and you can take the access back the same way you gave it.
What can it actually do in Blazemeter?
It has 20 ready-made tools in Blazemeter today, among them Create API Monitoring Schedule, Create Multi Test and Create Project. The full list is on this page. It is not limited to those, but it never has to be taught them.
Can it use Blazemeter and the rest of my software in the same job?
Yes, and that is usually the point. Reading a message in one app, checking a record in Blazemeter and writing the result somewhere else is one request to your AI employee, not three separate ones you stitch together.
Who decides what it is allowed to do in Blazemeter?
You do. You grant access one app at a time and can withdraw it at any time, anything you ask it to check with you first it checks with you first, and everything it does in Blazemeter is written down with what it did and when.