Install Jentic One Beta

Connect the Nowadays Public API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Nowadays Public API, 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%2Fnowadays.ai%2Fnowadays" | 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%2Fnowadays.ai%2Fnowadays" | 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 Nowadays Public API.

Create an event request with candidate cities in formattedLocations, eventDates ranges, and numPeople

Specify a guestroom block per night with room-type counts such as Single and Double in accommodations

Describe meeting-room needs with meetingRoomRequirements for the general session and breakouts

Update planning details such as budgetBreakdown, decisionDeadline, and flexibility without resending the whole event

GET STARTED

Start building with Nowadays Public API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use Nowadays Public API for, with concrete tasks.

★ AI assistant that files event requests

An operations assistant turns a chat request such as 'plan a three-day summit for 120 people in Austin or Denver' into a structured planning brief. Through Jentic the agent searches for 'create a corporate event request', gets the Nowadays create operation with its input schema, and sends the required name plus formattedLocations, eventDates, numPeople, and numHotelRoomsNeeded. The response returns the event's public id, which the agent keeps for later updates.

Call POST /v1/events with name 'Annual Summit', formattedLocations for Austin and Denver, eventDates 2027-03-15 to 2027-03-17, numPeople 120, and numHotelRoomsNeeded 60, then return the created id

Room block and meeting space specification

Hotel proposals depend on accurate room nights and meeting space. The Nowadays create operation accepts accommodations as one entry per night with the room-type split, and meetingRoomRequirements describes the general session and the number of breakouts. foodBeverageRequirements and flexibility carry the free-text needs that venues read when they respond.

Call POST /v1/events with name 'Sales Kickoff', accommodations of 60 Single and 11 Double for 2027-03-15, meetingRoomRequirements with a general session and 3 breakouts, and foodBeverageRequirements 'breakfast and lunch daily'

Keeping an event's plan current

Plans change after the first brief: headcount grows, budgets firm up, and a decision date is set. PATCH /v1/events/{id} changes only the fields sent, an explicit null clears a field, and if any field is rejected nothing is written. Budget goes in budgetBreakdown keyed by category such as venue, fb, and av.

Call PATCH /v1/events/{id} with numPeople 300, budgetBreakdown venue 120000 and fb 40000, and decisionDeadline 2026-09-01T00:00:00.000Z, then call GET /v1/events/{id} to confirm the change

Event pipeline status report

A planner wants a weekly summary of every event in flight. GET /v1/events lists the organization's events newest first with page and limit, returning each event's dates, locations, attendee count, and status, and GET /v1/events/{id} adds venue type, guestroom estimate, and notes. Results are scoped to what the key's user can open.

Call GET /v1/events with page 1 and limit 20, then report each event's name, dates, numPeople, and status, flagging any whose status is wait_for_proposals

Key Endpoints

4 endpoints — the nowadays public api creates and updates corporate event planning requests in a nowadays organization and reads them back.

METHOD

PATH

DESCRIPTION

POST

/v1/events

Create an event

GET

/v1/events

List events

GET

/v1/events/{id}

Get an event

PATCH

/v1/events/{id}

Update an event's planning details

POST

/v1/events

Create an event

GET

/v1/events

List events

GET

/v1/events/{id}

Get an event

PATCH

/v1/events/{id}

Update an event's planning details

Why Jentic?

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

Setup

Wiring Nowadays by hand means sending the x-api-key header, shaping nested room-block and meeting-room objects, and handling partial PATCH semantics where null clears a field. Through Jentic you install once, import Nowadays from the API Directory, store the key once, and your agent calls it.

Permission scoping

Nowadays puts the event id in the URL path (/v1/events/{id}), so a rule can pin your agent to the read or update operations for one event. You choose the operations it may call, so creating new events or editing existing ones is not included unless you add it.

Credential isolation

Your Nowadays API key is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'create a corporate event request' or 'update event budget', and Jentic returns the matching Nowadays operation with its input schema, including fields like accommodations and meetingRoomRequirements, so the agent sends a valid request directly.

FAQs

Specific to using Nowadays Public API through Jentic.

What authentication does the Nowadays Public API use?

Per its OpenAPI spec, the Nowadays Public API authenticates with an API key sent in the x-api-key header. The key belongs to an organization and a user: events you create land in that organization with the key's user as owner, and reads are scoped to what that user can open. Through Jentic the key is held by your own instance and injected at call time.

Can I update only some fields of an event with the Nowadays Public API?

Yes. PATCH /v1/events/{id} leaves omitted fields alone, clears a field when you send an explicit null, and writes nothing if any field is rejected. That makes it safe to send a single change such as a new numPeople or decisionDeadline.

What are the rate limits for the Nowadays Public API?

The OpenAPI spec does not specify rate limits. Check the Nowadays developer documentation at https://docs.nowadays.ai for current limits.

What is required to create an event with the Nowadays Public API?

Only name is required by the create schema. Everything else is optional, including formattedLocations, eventDates, numPeople, numHotelRoomsNeeded, accommodations, meetingRoomRequirements, foodBeverageRequirements, and currency, which defaults to USD. The response returns the new event's id and a grantedTo count of memberships given visibility.

How do I create an event request through Jentic?

Search Jentic for 'create a corporate event request', load the Nowadays create operation, and call POST /v1/events with a name and the cities, dates, and headcount you have. Keep the returned id so the agent can update the event later with PATCH /v1/events/{id}. To run it on your own infrastructure, install Jentic One from its GitHub repo.

Is there a Nowadays MCP server?

You do not need an MCP server to give your agent Nowadays. Jentic connects it directly from the API Directory: import it, store your API key once, and your agent calls the event operations it needs on demand.

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

Yes. For a reporting agent, write a rule that allows only GET /v1/events and GET /v1/events/{id}, so it can list events and read their status but cannot create or change them. Add POST /v1/events later if you want it to file new requests, and the calls it makes are logged for review.

Nowadays Public API

AI ReadinessFoundational (C)55/100

See full scorecard

Official vendor OpenAPI document · agent-readyProductivityCalendar SchedulingapiKey4 EndpointsREST

For Agents

Create a corporate event request with dates, cities, headcount, room block, and meeting-room needs in Nowadays, update its planning details and budget, and check its planning status.

Use for: Create an event request for a 120-person offsite in Austin next March, Add a hotel room block of 60 singles per night to my event, Set the venue decision deadline for our annual summit, Update the event budget for venue and food and beverage

Not supported: Does not sell tickets, register attendees, book flights, or return venue proposals. Use for creating, updating, and reading corporate event planning requests only.

The Nowadays Public API creates and updates corporate event planning requests in a Nowadays organization and reads them back. An event carries its name, candidate cities, date ranges, attendee count, venue type, guestroom block per night by room type, meeting-room and food and beverage requirements, date flexibility, and currency. Updates can also set a budget breakdown by category and a venue decision deadline, and the event's planning status, such as wait_for_proposals, is returned on read. Events are created in the organization the API key belongs to, and the key's user becomes the owner.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: ASignals: 4

98%

Lint Results

Aggregated quality score from linter diagnostics, weighted by severity.

100%

Resolution Completeness

Percentage of `$ref` references that resolve successfully.

100%

Specification Validity

Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).

30%

Structural Integrity

Structural correctness score based on schema issues using logarithmic dampening.

Developer Experience & Jentic Compatibility

Clarity, completeness, and ingestion readiness for developers and tooling.

Grade: A-Signals: 4

52%

Example Density

How richly the API is illustrated with examples.

92%

Example Validity

Percentage of examples that conform to their schemas.

50%

Response Coverage

Percentage of operations with complete response definitions (success, client error, server error).

100%

Tooling Readiness

Health of API ingestion, bundling, and resolution within Jentic pipelines.

AI-Readiness & Agent Experience

Semantic breadth, depth, and agent comprehension for AI systems.

Grade: FSignals: 4

56%

Description Coverage

Coverage of descriptions across API elements.

Error Standardization

Coverage of RFC 9457 Problem Details for error responses.

OperationId Quality

Coverage, uniqueness, and casing consistency of operationIds for AI inference.

67%

Summary Coverage

Coverage of summaries across operations/tags/info.

Agent Usability

Functional utility, complexity comfort, and AI orchestration readiness.

Grade: A+Signals: 1

94%

Complexity Comfort

Agent comfort level based on API operational and structural complexity.

Security

Trust, risk posture, and security compliance.

Grade: C-Signals: 1

50%

Authentication Strength

Average quality of security schemes based on authentication method strength (weakest link for OAuth2).

AI Discoverability

Findability, semantic richness, and reasoning readiness.

Grade: B-Signals: 1

62%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the Nowadays Public API to your agent

Capabilities

Start building with Nowadays Public API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

Nowadays Public API

Jentic AI Readiness Score

Nowadays Public API

Foundational Compliance

Lint Results

Resolution Completeness

Specification Validity

Structural Integrity

Developer Experience & Jentic Compatibility

Example Density

Example Validity

Response Coverage

Tooling Readiness

AI-Readiness & Agent Experience

Description Coverage

Error Standardization

OperationId Quality

Summary Coverage

Agent Usability

Complexity Comfort

Security

Authentication Strength

AI Discoverability

Descriptive Richness