Install Jentic One Beta

Connect the Noosh API application to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Noosh API application, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fnoosh.com%2Fnoosh" | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fnoosh.com%2Fnoosh" | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with Noosh API application API.

List and upload files into project workspaces with role-based notification

Read and update project specs that define the deliverable for vendors

Invite team members or full team templates to a project

List buy orders, billing recipients, and automatic invitations on a workgroup

Pull estimates and orders associated with marketing collateral projects

GET STARTED

Start building with Noosh API application API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use Noosh API application API for, with concrete tasks.

★ Print and packaging vendor handoff

Brand procurement teams running print and packaging campaigns use Noosh to centralise the spec, files, and approved vendors for each job. The API endpoints under /workgroups/{id}/projects/{id}/files and /specs lets an agent push the latest creative into Noosh and trigger a notification to vendors via /filesByRole, replacing email-based file shipping. This compresses the typical 'final files attached, please confirm receipt' email loop.

Upload a PDF to /1.1/workgroups/7/projects/12345/files with notification, then list /1.1/workgroups/7/projects/12345/fileTags to confirm tagging

Estimate and order reconciliation

Procurement managers reconciling vendor estimates against actual orders pull /estimates and /orders on the same project to compare quoted versus billed amounts. An agent can flag projects where actual orders exceed the highest estimate by more than a threshold, then route them for manager approval before invoices are paid.

List estimates and orders for project 12345, compare totals, and flag the project if actual exceeds estimate by 10%

Workgroup billing audit

Finance teams auditing vendor spend across a workgroup pull /buyOrders and /billingRecipients on a workgroup ID to see who is authorised to bill what. The /invoice endpoints surface issued invoices for cross-checking against the ERP. This produces an audit trail of spend by workgroup that finance can hand to internal audit.

List buy orders for workgroup 7 in the past quarter, then pull billing recipients to confirm authorisation for each vendor

AI agent for project setup

An AI assistant for a brand team can set up a new packaging project end to end: pull the workgroup, create the spec, upload the brief, and invite the approved vendors. Through Jentic, the agent finds each operation by intent rather than navigating Noosh's nested 100-plus endpoint tree manually.

Through Jentic, search 'invite a team member to a Noosh project', load /1.1/workgroups/{workgroup_id}/projects/{project_id}/teammembers, and execute

Key Endpoints

104 endpoints — noosh is a marketing project management platform used by brand and procurement teams to run print, packaging, and marketing collateral projects with vendors.

METHOD

PATH

DESCRIPTION

GET

/v1/workgroups

List workgroups on the account

GET

/v1/workgroups/{workgroup_id}/buyOrders

List buy orders for a workgroup

GET

/1.1/workgroups/{workgroup_id}/projects/{project_id}/files

List files on a project

POST

/1.1/workgroups/{workgroup_id}/projects/{project_id}/files

Upload a file to a project

GET

/1.1/workgroups/{workgroup_id}/projects/{project_id}/specs/{spec_id}

Read a project spec

POST

/1.1/workgroups/{workgroup_id}/projects/{project_id}/teammembers

Invite a team member to a project

GET

/v1/countries

List supported countries

GET

/v1/workgroups

List workgroups on the account

GET

/v1/workgroups/{workgroup_id}/buyOrders

List buy orders for a workgroup

GET

/1.1/workgroups/{workgroup_id}/projects/{project_id}/files

List files on a project

POST

/1.1/workgroups/{workgroup_id}/projects/{project_id}/files

Upload a file to a project

GET

/1.1/workgroups/{workgroup_id}/projects/{project_id}/specs/{spec_id}

Read a project spec

POST

/1.1/workgroups/{workgroup_id}/projects/{project_id}/teammembers

Invite a team member to a project

GET

/v1/countries

List supported countries

Why Jentic?

What agents get from Jentic-routed access to this vendor.

Setup

Wiring Noosh by hand means handling its basic auth, tracking the mixed /v1 and /1.1 path versions, and threading credentials through workgroup and project calls yourself across more than a hundred endpoints. Through Jentic you install once, import the Noosh API from the API Directory, store the credentials once, and your agent calls it.

Permission scoping

Noosh puts the workgroup and project ids in the URL path (/1.1/workgroups/{workgroup_id}/projects/{project_id}/...), so a rule can pin your agent to one workgroup or project. You choose the operations it may call, so posting new team members or files is not included unless you add it.

Credential isolation

Your Noosh basic-auth credentials are stored once, encrypted, by your own Jentic One instance and injected at execution time as the Authorization header. They never enter the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'upload a file to a project' or 'list buy orders', and Jentic returns the matching Noosh operation with its input schema so the agent calls the correct path version without browsing the reference docs.

FAQs

Specific to using Noosh API application API through Jentic.

What authentication does the Noosh API use?

Noosh uses HTTP Basic authentication. The username and password are issued by Noosh under your account contract; pass them on every request. Through Jentic, the credentials are stored in the encrypted vault and never enter the agent's prompt context.

Can I upload files to a Noosh project via the API?

Yes. POST a multipart/form-data request to /1.1/workgroups/{workgroup_id}/projects/{project_id}/files to upload a regular file, or /filesByRole to upload with role-based notification, or /1.2/.../filesByRole for the v1.2 variant with notification metadata.

Why does the Noosh API have multiple path versions like /v1, /1.1, and /1.2?

Noosh layered new operations as point releases without retiring older paths. /v1 holds workgroup-level reads such as /v1/countries and /v1/workgroups, while /1.1 and /1.2 hold the newer project-level file and team-member operations. Use the version that matches the operation in the spec rather than guessing.

What are the rate limits for the Noosh API?

Noosh does not publish a public rate limit and the spec does not encode one. Treat throughput as bound by your Noosh contract; for large file uploads, run them sequentially rather than in parallel to avoid back-pressure on the workgroup.

How do I list files on a Noosh project through Jentic?

Install with pip install jentic, then search 'list files in a Noosh project', load /1.1/workgroups/{workgroup_id}/projects/{project_id}/files, and execute with the workgroup and project IDs. The response includes file IDs that you can pass to the file detail endpoint.

Does the Noosh API expose financial data like invoices?

Yes. /v1/workgroups/{workgroup_id}/buyOrders and the invoice paths under projects expose buy orders and invoice records issued for project work. Pair these with an accounting API such as QuickBooks to reconcile against your ledger.

Can I limit what my agent is allowed to do with the Noosh API?

Yes. Because Jentic One is self-hosted, your own rules decide which Noosh operations and credentials the agent may use. Noosh puts workgroup and project IDs in the URL path, such as /1.1/workgroups/{workgroup_id}/projects/{project_id}/files, so you can pin the agent to a single workgroup or project. You also choose the allowed operations, so write actions like uploading files or inviting team members are excluded unless you grant them.

Noosh API application

Name: Noosh API application API
Brand: Noosh API application
Availability: InStock

Official vendor OpenAPI document · agent-readyProductivityCollaborationbasic104 EndpointsREST

For Agents

Manage marketing project workgroups, files, specs, estimates, and orders on Noosh on behalf of brand procurement and agency teams.

Use for: Upload a print-ready PDF to the spring campaign project on Noosh, List all files attached to project 12345 in workgroup 7, Update the spec for a packaging project before sending it out for bids, Invite a print vendor as a team member on a Noosh project

Not supported: Does not handle creative design, ad serving, or media buying - use for marketing project management, file handoff, and procurement workflows only.

Noosh is a marketing project management platform used by brand and procurement teams to run print, packaging, and marketing collateral projects with vendors. The API exposes workgroups, projects, files, specs, team members, estimates, orders, invoices, billing recipients, buy orders, exchange rates, and contact records, with separate v1.1, v1.2, and v1 path versions for different operations. Brand managers, agencies, and print buyers use it to integrate Noosh with ERPs, accounting tools, and asset management systems.

Jentic One on Github View OpenAPI Document

Connect the Noosh API application to your agent

Capabilities

Start building with Noosh API application API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

Noosh API application